[jira] [Created] (EAGLE-838) Resolve defunct process in hadoop jmx script by kill -9
Hao Chen created EAGLE-838: -- Summary: Resolve defunct process in hadoop jmx script by kill -9 Key: EAGLE-838 URL: https://issues.apache.org/jira/browse/EAGLE-838 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 * Resolve defunct process in hadoop jmx script by kill -9 * Support configurable log file path * Improve JMX reader to multiple-threading -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-833) Add MetricSchemaGenerator and MetricSchemaService
Hao Chen created EAGLE-833: -- Summary: Add MetricSchemaGenerator and MetricSchemaService Key: EAGLE-833 URL: https://issues.apache.org/jira/browse/EAGLE-833 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 * Add MetricSchemaService to store metric schema aside GenericMetric *Add MetricSchemaGenerator to automatically generate metric schema based on metric stream and metric definition. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-816) Fix host name bug in jmx collector scripts
Hao Chen created EAGLE-816: -- Summary: Fix host name bug in jmx collector scripts Key: EAGLE-816 URL: https://issues.apache.org/jira/browse/EAGLE-816 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 Fix host name bug in jmx collector scripts, which current always only use current fadn instead of configured host, it's a bug. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-815) Support alert template to generate human readable message
Hao Chen created EAGLE-815: -- Summary: Support alert template to generate human readable message Key: EAGLE-815 URL: https://issues.apache.org/jira/browse/EAGLE-815 Project: Eagle Issue Type: New Feature Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 Support alert template to generate human readable message * Support to define alert template in PolicyDefinition * Support to generate alert message field based on policy'template and alert event * Support persist alert message in AlertEntity as immutable field. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-807) Refactor JMX Metric Collector Script
Hao Chen created EAGLE-807: -- Summary: Refactor JMX Metric Collector Script Key: EAGLE-807 URL: https://issues.apache.org/jira/browse/EAGLE-807 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 Refactor JMX Metric Collector Script * Support multiple kafka topics * Support HA checking logic. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-806) Integrate Metric Process and Persistence with Application Framework
Hao Chen created EAGLE-806: -- Summary: Integrate Metric Process and Persistence with Application Framework Key: EAGLE-806 URL: https://issues.apache.org/jira/browse/EAGLE-806 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 Integrate Stream Source and Metric Persistence with Application Framework * Provide API to easily ingest, process, aggregate and persist metric * Integrate stream source * Integrate metric definition and metric persistence. * Implement basic plug-able aggregation abstraction for later usage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-792) Resolve google-fonts external connection blocking problem in AdminLTE
Hao Chen created EAGLE-792: -- Summary: Resolve google-fonts external connection blocking problem in AdminLTE Key: EAGLE-792 URL: https://issues.apache.org/jira/browse/EAGLE-792 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Jilin, Jiang Fix For: v0.5.0 Resolve google-fonts connection problem in AdminLTE when having no access to external network. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-791) Refactor eagle module names to be more meaningful
Hao Chen created EAGLE-791:
--
Summary: Refactor eagle module names to be more meaningful
Key: EAGLE-791
URL: https://issues.apache.org/jira/browse/EAGLE-791
Project: Eagle
Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
Fix For: v0.5.0
Refactor eagle module names to be more meaningful for developer to learn about
eagle's code structure.
{code}
[INFO] Eagle::Parent .. SUCCESS [ 0.204 s]
[INFO] Eagle::Core::Parent SUCCESS [ 0.003 s]
[INFO] Eagle::Core::DataProcess ... SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Common SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Alert . SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Alert::Core ... SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Alert::Common . SUCCESS [ 0.026 s]
[INFO] Eagle::Core::Alert::Engine . SUCCESS [ 0.004 s]
[INFO] Eagle::Core::Alert::Metadata ... SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Alert::MetadataBase ... SUCCESS [ 0.003 s]
[INFO] Eagle::Core::Alert::MetadataService SUCCESS [ 0.003 s]
[INFO] Eagle::Core::Alert::Coordinator SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Alert::Assembly ... SUCCESS [ 0.003 s]
[INFO] Eagle::Core::Alert::DevTools ... SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Alert::ServiceApp . SUCCESS [ 0.001 s]
[INFO] Eagle::Core::Query::Parent . SUCCESS [ 0.003 s]
[INFO] Eagle::Core::Query::Antlr .. SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Embed::Parent . SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Embed::HBase .. SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Query::EntityBase . SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Query::Base ... SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Query::StorageBase SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Embed::Server . SUCCESS [ 0.001 s]
[INFO] Eagle::Core::Client::Base .. SUCCESS [ 0.003 s]
[INFO] Eagle::Core::Query::Audit .. SUCCESS [ 0.001 s]
[INFO] Eagle::Core::Query::HBaseStorage ... SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Service::Base . SUCCESS [ 0.003 s]
[INFO] Eagle::Core::Metadata .. SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Metadata::Base SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Alert::Service SUCCESS [ 0.003 s]
[INFO] Eagle::Core::App::Parent ... SUCCESS [ 0.002 s]
[INFO] Eagle::Core::App::Base . SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Alert::AppProvider SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Query::JDBCStorage SUCCESS [ 0.003 s]
[INFO] Eagle::Core::Metric SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Metadata::JDBC SUCCESS [ 0.002 s]
[INFO] Eagle::Core::Metadata::MongoDB . SUCCESS [ 0.001 s]
[INFO] Eagle::Core::App::Utils SUCCESS [ 0.001 s]
[INFO] Eagle::App::Security::Parent ... SUCCESS [ 0.002 s]
[INFO] Eagle::App::Security::Common ... SUCCESS [ 0.002 s]
[INFO] Eagle::App::Security::HdfsAuditLog . SUCCESS [ 0.002 s]
[INFO] Eagle::App::Security::MapRFSAuditLog ... SUCCESS [ 0.001 s]
[INFO] Eagle::App::JPM::Parent SUCCESS [ 0.002 s]
[INFO] Eagle::App::JPM::Utils . SUCCESS [ 0.001 s]
[INFO] Eagle::App::Security::HiveSecurity . SUCCESS [ 0.001 s]
[INFO] Eagle::App::Security::HiveService .. SUCCESS [ 0.002 s]
[INFO] Eagle::App::Security::HdfsService .. SUCCESS [ 0.001 s]
[INFO] Eagle::App::Security::MapRFSService SUCCESS [ 0.001 s]
[INFO] Eagle::App::Security::HdfsAuthLog .. SUCCESS [ 0.001 s]
[INFO] Eagle::App::Security::HBaseAuditLog SUCCESS [ 0.002 s]
[INFO] Eagle::App::Security::HBaseService . SUCCESS [ 0.001 s]
[INFO] Eagle::App::Security::MetricCollection . SUCCESS [ 0.001 s]
[INFO] Eagle::App::Security::OozieAuditLog SUCCESS [ 0.001 s]
[INFO] Eagle::App::Security::OozieService . SUCCESS [ 0.001 s]
[INFO] Eagle::External::Parent SUCCESS [ 0.001 s]
[INFO] Eagle::External::Log4jKafkaAppender SUCCESS
[jira] [Resolved] (EAGLE-769) InjectMembers in ServerApplication when initialization
[ https://issues.apache.org/jira/browse/EAGLE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-769. Resolution: Fixed > InjectMembers in ServerApplication when initialization > -- > > Key: EAGLE-769 > URL: https://issues.apache.org/jira/browse/EAGLE-769 > Project: Eagle > Issue Type: Improvement >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > InjectMembers in ServerApplication when initialization -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-769) InjectMembers in ServerApplication when initialization
Hao Chen created EAGLE-769: -- Summary: InjectMembers in ServerApplication when initialization Key: EAGLE-769 URL: https://issues.apache.org/jira/browse/EAGLE-769 Project: Eagle Issue Type: Improvement Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 InjectMembers in ServerApplication when initialization -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-766) Set default host of JPM_WEB_APP as null
[ https://issues.apache.org/jira/browse/EAGLE-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-766: --- Summary: Set default host of JPM_WEB_APP as null (was: Set default host of JPM_WEB_APP as N/A) > Set default host of JPM_WEB_APP as null > > > Key: EAGLE-766 > URL: https://issues.apache.org/jira/browse/EAGLE-766 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Hao Chen > Fix For: v0.5.0 > > > Set default host & port of JPM_WEB_APP as N/A to make sure the web will read > web service from configured instead of always using current. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-766) Set default host of JPM_WEB_APP as N/A
Hao Chen created EAGLE-766: -- Summary: Set default host of JPM_WEB_APP as N/A Key: EAGLE-766 URL: https://issues.apache.org/jira/browse/EAGLE-766 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Hao Chen Fix For: v0.5.0 Set default host & port of JPM_WEB_APP as N/A to make sure the web will read web service from configured instead of always using current. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-5) Minimal general-purpose monitoring engine
[ https://issues.apache.org/jira/browse/EAGLE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-5. -- Resolution: Fixed > Minimal general-purpose monitoring engine > -- > > Key: EAGLE-5 > URL: https://issues.apache.org/jira/browse/EAGLE-5 > Project: Eagle > Issue Type: New Feature >Reporter: Hao Chen >Assignee: Hao Chen > > As the first step, we should allow traditional monitoring 'users' to > 1. Create kafka topic say > 2. Configure stream on UI > 3. Start generic KafkaStreamMonitor topology pointing to the kafka and stream > "storm jar KafkaStreamMonitor --topic $kafka_topic_name --stream > $configured_stream_name " > 4. Then user could start to define policy with eagle policy manager UI > As the second step, we should allow 'developers' to define stream schema, > transformation and alert pipeline in very easily way, schema metadata could > be defined from inline / file / database (UI), as to inline/file way, the > framework will finally sync the stream schema into database (UI), so that > make sure the single source of truth. > As the third step, we may create a never-existed experience as what you > described. We could allow user to define end-to-end monitoring stream > pipeline with UI: > 1. DAG Builder > 1) Set Data Source > 2) Set Stream Schema > 3) Define Transformation with simple method or advanced programming scripts > like groovy > 4) Connect to Alert Engine > 2. DAG Manager > 1) Automatically build DAG > 2) Automatically schedule DAG -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-32) Mininal General KafkaStreamMonitor
[ https://issues.apache.org/jira/browse/EAGLE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-32. --- Resolution: Won't Fix > Mininal General KafkaStreamMonitor > -- > > Key: EAGLE-32 > URL: https://issues.apache.org/jira/browse/EAGLE-32 > Project: Eagle > Issue Type: Sub-task > Environment: development >Reporter: Hao Chen >Assignee: Hao Chen > > As the first step, we should allow traditional monitoring 'users' to > 1. Create kafka topic say > 2. Configure stream on UI > 3. Start generic KafkaStreamMonitor topology pointing to the kafka and stream > "storm jar KafkaStreamMonitor --topic $kafka_topic_name --stream > $configured_stream_name " > 4. Then user could start to define policy with eagle policy manager UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-20) Support Filebeat as Log Shipper for better performance
[ https://issues.apache.org/jira/browse/EAGLE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-20. --- Resolution: Fixed Assignee: Zhao, Qingwen (was: Hao Chen) > Support Filebeat as Log Shipper for better performance > -- > > Key: EAGLE-20 > URL: https://issues.apache.org/jira/browse/EAGLE-20 > Project: Eagle > Issue Type: New Feature >Reporter: Hao Chen >Assignee: Zhao, Qingwen > > Currently we provide two approaches for user to ship hadoop audit log from > local to kafka, while they have some problems for large log flow > 1) log4j kafka appender: impact hadoop name node stability > 2) logstash: consume too many machine resource like CPU/Memory > So we may need to evaluate some other possible solutions like Elastic > Filebeat: https://github.com/elastic/filebeat -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-146) SiddhiExtensionLoader Error: viewing zip file for jar:./lib/ojdbc6.jar
[
https://issues.apache.org/jira/browse/EAGLE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen resolved EAGLE-146.
Resolution: Won't Fix
> SiddhiExtensionLoader Error: viewing zip file for jar:./lib/ojdbc6.jar
> --
>
> Key: EAGLE-146
> URL: https://issues.apache.org/jira/browse/EAGLE-146
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> {code}
> 2016-02-02 02:46:23 o.a.e.p.PolicyManager [INFO] Supported policy type :
> siddhiCEPEngine
> 2016-02-02 02:46:23 o.a.e.p.PolicyManager [INFO] Supported policy type :
> MachineLearning
> 2016-02-02 02:46:23 o.w.s.c.u.SiddhiExtensionLoader [ERROR] Error viewing zip
> file for jar:./lib/ojdbc6.jar
> java.io.FileNotFoundException: ./lib/ojdbc6.jar (No such file or directory)
> at java.util.zip.ZipFile.open(Native Method) ~[na:1.7.0_60]
> at java.util.zip.ZipFile.(ZipFile.java:215) ~[na:1.7.0_60]
> at java.util.zip.ZipFile.(ZipFile.java:145) ~[na:1.7.0_60]
> at java.util.zip.ZipFile.(ZipFile.java:159) ~[na:1.7.0_60]
> at
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContentFromJarFile(SiddhiExtensionLoader.java:111)
> [stormjar.jar:na]
> at
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContent(SiddhiExtensionLoader.java:82)
> [stormjar.jar:na]
> at
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContentFromDirectory(SiddhiExtensionLoader.java:101)
> [stormjar.jar:na]
> at
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContent(SiddhiExtensionLoader.java:77)
> [stormjar.jar:na]
> at
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContentFromDirectory(SiddhiExtensionLoader.java:101)
> [stormjar.jar:na]
> at
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContent(SiddhiExtensionLoader.java:77)
> [stormjar.jar:na]
> at
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getResources(SiddhiExtensionLoader.java:71)
> [stormjar.jar:na]
> at
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.loadSiddhiExtensions(SiddhiExtensionLoader.java:51)
> [stormjar.jar:na]
> at
> org.wso2.siddhi.core.config.SiddhiContext.(SiddhiContext.java:35)
> [stormjar.jar:na]
> at org.wso2.siddhi.core.SiddhiManager.(SiddhiManager.java:40)
> [stormjar.jar:na]
> at
> org.apache.eagle.policy.siddhi.SiddhiPolicyEvaluator.createSiddhiRuntime(SiddhiPolicyEvaluator.java:108)
> [stormjar.jar:na]
> at
> org.apache.eagle.policy.siddhi.SiddhiPolicyEvaluator.init(SiddhiPolicyEvaluator.java:83)
> [stormjar.jar:na]
> at
> org.apache.eagle.policy.siddhi.SiddhiPolicyEvaluator.(SiddhiPolicyEvaluator.java:79)
> [stormjar.jar:na]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) [na:1.7.0_60]
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> [na:1.7.0_60]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> [na:1.7.0_60]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> [na:1.7.0_60]
> at
> org.apache.eagle.policy.executor.PolicyProcessExecutor.createPolicyEvaluator(PolicyProcessExecutor.java:243)
> [stormjar.jar:na]
> at
> org.apache.eagle.policy.executor.PolicyProcessExecutor.init(PolicyProcessExecutor.java:188)
> [stormjar.jar:na]
> at
> org.apache.eagle.datastream.storm.JavaStormBoltWrapper.prepare(JavaStormBoltWrapper.scala:36)
> [stormjar.jar:na]
> at
> backtype.storm.daemon.executor$fn__5697$fn__5710.invoke(executor.clj:732)
> [storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
> at backtype.storm.util$async_loop$fn__452.invoke(util.clj:463)
> [storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
> at clojure.lang.AFn.run(AFn.java:24) [clojure-1.5.1.jar:na]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]
> 2016-02-02 02:46:23 o.w.s.c.u.SiddhiExtensionLoader [ERROR] Error viewing zip
> file for jar:./lib/ojdbc6.jar
> java.io.FileNotFoundException: ./lib/ojdbc6.jar (No such file or directory)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (EAGLE-184) Migrate eagle website from https://github.com/eaglemonitoring/eaglemonitoring.github.io to document branch
[ https://issues.apache.org/jira/browse/EAGLE-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-184. Resolution: Won't Fix > Migrate eagle website from > https://github.com/eaglemonitoring/eaglemonitoring.github.io to document > branch > -- > > Key: EAGLE-184 > URL: https://issues.apache.org/jira/browse/EAGLE-184 > Project: Eagle > Issue Type: New Feature >Reporter: Hao Chen >Assignee: Hao Chen > > Migrate eagle website from > https://github.com/eaglemonitoring/eaglemonitoring.github.io to document > branch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-129) Eagle Declarative Pipeline
[ https://issues.apache.org/jira/browse/EAGLE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-129. Resolution: Won't Fix > Eagle Declarative Pipeline > -- > > Key: EAGLE-129 > URL: https://issues.apache.org/jira/browse/EAGLE-129 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.3.0 >Reporter: Hao Chen >Assignee: Hao Chen > > https://cwiki.apache.org/confluence/display/EAG/Dynamical+Monitoring+Framework -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-167) Refine JMX Collector Code
[ https://issues.apache.org/jira/browse/EAGLE-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-167. Resolution: Fixed > Refine JMX Collector Code > - > > Key: EAGLE-167 > URL: https://issues.apache.org/jira/browse/EAGLE-167 > Project: Eagle > Issue Type: Improvement >Reporter: Hao Chen >Assignee: Hao Chen > > * Refactor JMX Collector to load extensions from external directory -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-181) HDFS topology alerts multiple time.
[ https://issues.apache.org/jira/browse/EAGLE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-181. Resolution: Fixed > HDFS topology alerts multiple time. > > > Key: EAGLE-181 > URL: https://issues.apache.org/jira/browse/EAGLE-181 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.3.0 >Reporter: hemanth dendukuri >Assignee: Hao Chen > Labels: pre-release > > when I trigger an event of HDFS to create a alert > > hadoop fs -cat /tmp/private > Actual > - > I saw 9 alerts were create for single violation. Each alert was created in a > gap of minute. > Expected > - > Only one alert should be created for single violation. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-393) Fix UnitTest Error caused by streamDef.json and TestApplicationImpl
[ https://issues.apache.org/jira/browse/EAGLE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-393. Resolution: Fixed > Fix UnitTest Error caused by streamDef.json and TestApplicationImpl > --- > > Key: EAGLE-393 > URL: https://issues.apache.org/jira/browse/EAGLE-393 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.4.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > Fix UnitTest Error caused by streamDef.json and TestApplicationImpl -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-480) Make Hadoop jmx monitoring working in Eagle 0.5
[ https://issues.apache.org/jira/browse/EAGLE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-480. Resolution: Fixed > Make Hadoop jmx monitoring working in Eagle 0.5 > --- > > Key: EAGLE-480 > URL: https://issues.apache.org/jira/browse/EAGLE-480 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Edward Zhang >Assignee: Hao Chen > Fix For: v0.5.0 > > > Hadoop jmx metrics data will go to alert engine directly, we need verify how > to create data source, stream and policies in Eagle 0.5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-413) Fix Unit Test org.apache.eagle.alert.siddhi.TestExternalBatchWindow
[
https://issues.apache.org/jira/browse/EAGLE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen resolved EAGLE-413.
Resolution: Fixed
> Fix Unit Test org.apache.eagle.alert.siddhi.TestExternalBatchWindow
> ---
>
> Key: EAGLE-413
> URL: https://issues.apache.org/jira/browse/EAGLE-413
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Labels: unit-test
> Fix For: v0.4.0, v0.3.0
>
>
> org.wso2.siddhi.query.api.exception.ExecutionPlanValidationException: No
> extension exist for WindowExtension{namespace='eagle'} , when creating query
> pull76 in execution plan "1b43d978-cf66-465b-a6be-ac251025d85d"
> at
> org.wso2.siddhi.core.util.parser.ExecutionPlanParser.parse(ExecutionPlanParser.java:185)
> at
> org.wso2.siddhi.core.SiddhiManager.createExecutionPlanRuntime(SiddhiManager.java:59)
> at
> org.wso2.siddhi.core.SiddhiManager.createExecutionPlanRuntime(SiddhiManager.java:73)
> at
> org.apache.eagle.alert.siddhi.TestExternalBatchWindow.test07Pull76(TestExternalBatchWindow.java:170)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:119)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
> at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: org.wso2.siddhi.core.exception.ExecutionPlanCreationException: No
> extension exist for WindowExtension{namespace='eagle'} , when creating query
> pull76
> at
> org.wso2.siddhi.core.util.parser.QueryParser.parse(QueryParser.java:195)
> at
> org.wso2.siddhi.core.util.parser.ExecutionPlanParser.parse(ExecutionPlanParser.java:169)
> ... 40 more
> Caused by: org.wso2.siddhi.core.exception.ExecutionPlanCreationException: No
> extension exist for WindowExtension{namespace='eagle'}
> at
> org.wso2.siddhi.core.util.SiddhiClassLoader.loadExtensionImplementation(SiddhiClassLoader.java:67)
> at
>
[jira] [Resolved] (EAGLE-391) Integrate Application start/stop/status interface with TopologyMgmtResourceImpl
[ https://issues.apache.org/jira/browse/EAGLE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-391. Resolution: Won't Fix > Integrate Application start/stop/status interface with > TopologyMgmtResourceImpl > --- > > Key: EAGLE-391 > URL: https://issues.apache.org/jira/browse/EAGLE-391 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.4.0 >Reporter: Hao Chen >Assignee: Hao Chen >Priority: Minor > Fix For: v0.5.0 > > > Integrate Application start/stop/status interface with > TopologyMgmtResourceImpl -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-405) hadoopJmxMetricAlertExecutor ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/EAGLE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen resolved EAGLE-405.
Resolution: Won't Fix
> hadoopJmxMetricAlertExecutor ArrayIndexOutOfBoundsException
> ---
>
> Key: EAGLE-405
> URL: https://issues.apache.org/jira/browse/EAGLE-405
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0, v0.4.1
>
>
> {code}
> 2016-08-01T05:12:01.054+ o.a.e.p.e.PolicyProcessExecutor [ERROR]
> hadoopJmxMetricAlertExecutor, partition 0, error fetching alerts, but
> continue to run
> java.lang.ArrayIndexOutOfBoundsException: null
> Hope we fixed this ArrayIndexOutOfBoundException
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (EAGLE-387) Implement Application Lifecycle Status Conversion
[
https://issues.apache.org/jira/browse/EAGLE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen resolved EAGLE-387.
Resolution: Fixed
> Implement Application Lifecycle Status Conversion
> -
>
> Key: EAGLE-387
> URL: https://issues.apache.org/jira/browse/EAGLE-387
> Project: Eagle
> Issue Type: Sub-task
>Affects Versions: v0.4.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> {code}
> public static enum Status{
> INITIAILIZED("INITIAILIZED"),
> STARTING("STARTING"),
> RUNNING("RUNNING"),
> STOPPPING("STOPPPING"),
> STOPPED("STOPPED");
> private final String status;
> Status(String status){
> this.status = status;
> }
> @Override
> public String toString() {
> return status;
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (EAGLE-233) Integrate [maven-release-plugin] for eagle release
[ https://issues.apache.org/jira/browse/EAGLE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-233. Resolution: Fixed > Integrate [maven-release-plugin] for eagle release > -- > > Key: EAGLE-233 > URL: https://issues.apache.org/jira/browse/EAGLE-233 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.3.0 >Reporter: Hao Chen >Assignee: Hao Chen > Labels: development, tools > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-459) Convert spark history using new app framework
[ https://issues.apache.org/jira/browse/EAGLE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-459. Resolution: Fixed > Convert spark history using new app framework > - > > Key: EAGLE-459 > URL: https://issues.apache.org/jira/browse/EAGLE-459 > Project: Eagle > Issue Type: Sub-task >Reporter: Hao Chen >Assignee: Hao Chen > > Convert spark history using new app framework -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-596) Caught NoSuchFieldError when creating policy with existing policyId
[
https://issues.apache.org/jira/browse/EAGLE-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen resolved EAGLE-596.
Resolution: Won't Fix
> Caught NoSuchFieldError when creating policy with existing policyId
> ---
>
> Key: EAGLE-596
> URL: https://issues.apache.org/jira/browse/EAGLE-596
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Jilin, Jiang
>Assignee: Hao Chen
> Labels: alert-engine, alert-service, metadata
> Fix For: v0.5.0
>
>
> h2. Sample Data
> {code}
> {"name":"Mock","description":"asdadsasd","inputStreams":["hbase_audit_log_stream"],"outputStreams":["hbase_audit_log_stream"],"definition":{"type":"siddhi","value":"test","handlerClass":null,"properties":{},"inputStreams":[],"outputStreams":[]},"partitionSpec":[],"parallelismHint":2}
> {code}
> h2. NoSuchFieldError
> {code}
> WARN [2016-10-09 09:42:35,636] org.eclipse.jetty.servlet.ServletHandler:
> Error for /rest/metadata/policies
> ! java.lang.NoSuchFieldError: _nullProvider
> ! at
> com.fasterxml.jackson.module.afterburner.deser.OptimizedSettableBeanProperty._deserializeString(OptimizedSettableBeanProperty.java:168)
> ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at
> com.fasterxml.jackson.module.afterburner.deser.SettableStringMethodProperty.deserializeAndSet(SettableStringMethodProperty.java:54)
> ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
> ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
> ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at
> com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:520)
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at
> com.fasterxml.jackson.module.afterburner.deser.SettableObjectMethodProperty.deserializeAndSet(SettableObjectMethodProperty.java:53)
> ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:226)
> ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserialize(SuperSonicBeanDeserializer.java:118)
> ~[jackson-module-afterburner-2.3.3.jar:2.3.3]
> ! at
> com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:1470)
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at
> com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:912)
> ~[jackson-databind-2.6.6.jar:2.6.6]
> ! at
> com.fasterxml.jackson.jaxrs.base.ProviderBase.readFrom(ProviderBase.java:811)
> ~[jackson-jaxrs-base-2.6.6.jar:2.6.6]
> ! at
> io.dropwizard.jersey.jackson.JacksonMessageBodyProvider.readFrom(JacksonMessageBodyProvider.java:60)
> ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at
> com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
> ~[jersey-server-1.19.1.jar:1.19.1]
> ! at
> com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
> ~[jersey-server-1.19.1.jar:1.19.1]
> ! at
> com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
> ~[jersey-server-1.19.1.jar:1.19.1]
> ! at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
> ~[jersey-server-1.19.1.jar:1.19.1]
> ! at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:183)
> ~[jersey-server-1.19.1.jar:1.19.1]
> ! at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> ~[jersey-server-1.19.1.jar:1.19.1]
> ! at
> io.dropwizard.jersey.guava.OptionalResourceMethodDispatchAdapter$OptionalRequestDispatcher.dispatch(OptionalResourceMethodDispatchAdapter.java:37)
> ~[dropwizard-jersey-0.7.1.jar:0.7.1]
> ! at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> ~[jersey-server-1.19.1.jar:1.19.1]
> ! at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> ~[jersey-server-1.19.1.jar:1.19.1]
> ! at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> ~[jersey-server-1.19.1.jar:1.19.1]
> ! at
>
[jira] [Resolved] (EAGLE-613) Support modify ApplicationEntity through POST /rest/apps/{UUID}/
[
https://issues.apache.org/jira/browse/EAGLE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen resolved EAGLE-613.
Resolution: Fixed
> Support modify ApplicationEntity through POST /rest/apps/{UUID}/
>
>
> Key: EAGLE-613
> URL: https://issues.apache.org/jira/browse/EAGLE-613
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Support modify ApplicationEntity through
> {code}
> POST /rest/apps/{UUID}/
> {code}
> * REQUEST BODY*
> ApplicationEntity (without streams)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (EAGLE-639) Generate sortSpec only on externalWindow
[ https://issues.apache.org/jira/browse/EAGLE-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-639. Resolution: Fixed > Generate sortSpec only on externalWindow > > > Key: EAGLE-639 > URL: https://issues.apache.org/jira/browse/EAGLE-639 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > Generate sortSpec only on externalWindow -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-654) Fix alert engine open metric system per tuple
[ https://issues.apache.org/jira/browse/EAGLE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-654. Resolution: Fixed > Fix alert engine open metric system per tuple > - > > Key: EAGLE-654 > URL: https://issues.apache.org/jira/browse/EAGLE-654 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > Currently alert engine open metric system per tuple which will waste > connection and throughput: > https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/runner/AlertBolt.java#L131 > In order to export metric in eagle, app developer (including alert engine) > should never touch MetricSystem directly but should use storm native metric > framework to declare and update metric, and eagle framework will > automatically receive metrics and export as configured. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-635) Refactor policy parser and validator for richer plan details and better performance
[
https://issues.apache.org/jira/browse/EAGLE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen resolved EAGLE-635.
Resolution: Fixed
> Refactor policy parser and validator for richer plan details and better
> performance
> ---
>
> Key: EAGLE-635
> URL: https://issues.apache.org/jira/browse/EAGLE-635
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> h2. Changes
> * Refactor policy parser and validator for richer plan details and better
> performance
> * Decouple PolicyExecutionPlan and PolicyValidation
> h2. API
> * Parse API
> {code}
> POST /metadata/policies/parse
> Accept-Type: text
> from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select
> cmd, user, count() as total_count group by cmd,user insert into
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
> {code}
> * Validation API
> {code}
> POST /metadata/policies/validate
> Accept-Type: application/json
> {
>"name": "hdfsPolicy",
>"description": "hdfsPolicy",
>"inputStreams": [
> "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
>],
>"outputStreams": [
> "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
>],
>"definition": {
> "type": "siddhi",
> "value": "from
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd,
> user, count() as total_count group by cmd,user insert into
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
>},
>"partitionSpec": [
> {
> "streamId": "hdfs_audit_log_enriched_stream",
> "type": "GROUPBY",
> "columns" : [
> "cmd"
> ]
> }
>],
>"parallelismHint": 2
> }
> {code}
> h2. Use Cases
> * *parse*: could continuously call `parse` API aside during user keeps typing
> to verify the syntax and automatically generate input/output/partition , as
> it won't call back-end db, so will be very fast.
> * *validate*: when user finishes defining policy, the api will validate the
> metadata end2end
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (EAGLE-647) Support Policy Execution Interpreter and Planner to compile siddhi query to distributed execution plan
[ https://issues.apache.org/jira/browse/EAGLE-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-647. Resolution: Fixed > Support Policy Execution Interpreter and Planner to compile siddhi query to > distributed execution plan > -- > > Key: EAGLE-647 > URL: https://issues.apache.org/jira/browse/EAGLE-647 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > Support Policy Execution Interpreter and Planner to compile siddhi query to > distributed execution plan > * Support parse siddhi pattern and join query as distributed execution > * Support alias in inner join condition > * Refactor PolicyIntepreter to eagle-alert-engine and decoupel > PolicyExecutionPlanner > * Fix factory method for PolicyExecutionPlanner -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-663) Build git head COMMITID into eagle package and display in web page aside eagle version
[
https://issues.apache.org/jira/browse/EAGLE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen resolved EAGLE-663.
Resolution: Fixed
> Build git head COMMITID into eagle package and display in web page aside
> eagle version
> --
>
> Key: EAGLE-663
> URL: https://issues.apache.org/jira/browse/EAGLE-663
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> {code}
> # Get git-head commit ID
> COMMITID=`git rev-parse HEAD`
> # Get current maven version
> VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}'
> --non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
> DATE=`date`
> # Generate
> classes/assets/build-version.json
> # Access as static resource
> /build-version.json
> {
> version: "$VERSION"
> commit: "$COMMITID"
> built: "$, MacOSX, 1.8.0_74-b02"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (EAGLE-711) Document JMX monitoring application
[ https://issues.apache.org/jira/browse/EAGLE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-711. Resolution: Fixed > Document JMX monitoring application > --- > > Key: EAGLE-711 > URL: https://issues.apache.org/jira/browse/EAGLE-711 > Project: Eagle > Issue Type: Task >Reporter: jianzhong.chen >Assignee: Hao Chen > Labels: docuentation > Fix For: v0.5.0 > > > Application description along with: > - what to be monitored > - how to collect data, any expected impact to monitored service > - how to define a policy, especially on how to extract the fields from > stream? > - as much as supported policy examples > - latency expected for alert > - how to troubleshooting an application if any failure happens? > - .. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-716) [API] Validate before saving policy
[
https://issues.apache.org/jira/browse/EAGLE-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen resolved EAGLE-716.
Resolution: Fixed
> [API] Validate before saving policy
> ---
>
> Key: EAGLE-716
> URL: https://issues.apache.org/jira/browse/EAGLE-716
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> [API] Forcefully Validate before saving policy into metadata when calling
> {code}
> POST /policies
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (EAGLE-734) Integrate maven-buildNumber-plugin and Version.java
[ https://issues.apache.org/jira/browse/EAGLE-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-734. Resolution: Fixed > Integrate maven-buildNumber-plugin and Version.java > --- > > Key: EAGLE-734 > URL: https://issues.apache.org/jira/browse/EAGLE-734 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > * Integrate maven-buildNumber-plugin and Version.java > * Format eagle version desc > * Add `/server/version` and `/server/config` API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-762) Add AlertEmailPublisherTest test cases
[ https://issues.apache.org/jira/browse/EAGLE-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-762. Resolution: Fixed > Add AlertEmailPublisherTest test cases > -- > > Key: EAGLE-762 > URL: https://issues.apache.org/jira/browse/EAGLE-762 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > Add AlertEmailPublisherTest test cases -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-762) Add AlertEmailPublisherTest test cases
Hao Chen created EAGLE-762: -- Summary: Add AlertEmailPublisherTest test cases Key: EAGLE-762 URL: https://issues.apache.org/jira/browse/EAGLE-762 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 Add AlertEmailPublisherTest test cases -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-581) Generate a build number when building the project.
[ https://issues.apache.org/jira/browse/EAGLE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-581. Resolution: Duplicate > Generate a build number when building the project. > -- > > Key: EAGLE-581 > URL: https://issues.apache.org/jira/browse/EAGLE-581 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Huizhi Lu >Assignee: Huizhi Lu > Fix For: v0.5.0 > > > Use case: > we need to know what version(latest commit revision) of source code we are > using for the current build so that it will be convenient for us to clarify > different builds. So when you might make 100 builds of version > 0.5.0-SNAPSHOT, you can differentiate between them all. > Solution: > Use buildnumber-maven-plugin > 1. Add Maven plugin buildnumber-maven-plugin to pom.xml file > 2. Add manifest entries to META-INF/MANIFEST.MF > Build-Branch: EAGLE-581 > Build-Commit: f6fad2ebe8a384a6d17e40c609041ff77f6a692c > Build-Time: 2016-10-02 09:05:31 AM, UTC > 3. Placehold VERSION. > The build info is stored in RELEASE File in the root directory. RELEASE is > like: > project.version: 0.5.0-incubating-SNAPSHOT > build.branch: EAGLE-581 > build.commit: f6fad2ebe8a384a6d17e40c609041ff77f6a692c > build.time: 2016-10-02 01:39:40 AM, PDT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-752) JPM statistic need remove jobType
[ https://issues.apache.org/jira/browse/EAGLE-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-752: --- Description: JPM statistic need remove jobType > JPM statistic need remove jobType > - > > Key: EAGLE-752 > URL: https://issues.apache.org/jira/browse/EAGLE-752 > Project: Eagle > Issue Type: Bug >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > > JPM statistic need remove jobType -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-739) Fix eagle-metric checkstyle warnings
[ https://issues.apache.org/jira/browse/EAGLE-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-739: --- Assignee: luokun > Fix eagle-metric checkstyle warnings > > > Key: EAGLE-739 > URL: https://issues.apache.org/jira/browse/EAGLE-739 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.4.0 >Reporter: luokun >Assignee: luokun > Fix For: v0.5.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > Fix checkstyle problems on eagle-metric -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-740) Fix eagle-query checkstyle warnings
[ https://issues.apache.org/jira/browse/EAGLE-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-740: --- Assignee: luokun > Fix eagle-query checkstyle warnings > --- > > Key: EAGLE-740 > URL: https://issues.apache.org/jira/browse/EAGLE-740 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.4.0 >Reporter: luokun >Assignee: luokun > Fix For: v0.5.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > Fix checkstyle problems on eagle-query -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-716) [API] Validate before saving policy
Hao Chen created EAGLE-716:
--
Summary: [API] Validate before saving policy
Key: EAGLE-716
URL: https://issues.apache.org/jira/browse/EAGLE-716
Project: Eagle
Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
Fix For: v0.5.0
[API] Forcefully Validate before saving policy into metadata when calling
{code}
POST /policies
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (EAGLE-678) Support to configure links for site
Hao Chen created EAGLE-678: -- Summary: Support to configure links for site Key: EAGLE-678 URL: https://issues.apache.org/jira/browse/EAGLE-678 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 Support to configure links for site. As to Hadoop, support set: * Name Node URL * Resource Manager URL As to HBase, support: * HBase master URL Spark: * Spark History Server URL -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-677) Hadoop JMX Collector Support HA switching
Hao Chen created EAGLE-677: -- Summary: Hadoop JMX Collector Support HA switching Key: EAGLE-677 URL: https://issues.apache.org/jira/browse/EAGLE-677 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-676) Package hadoop jmx metric collector into eagle pacakge
Hao Chen created EAGLE-676: -- Summary: Package hadoop jmx metric collector into eagle pacakge Key: EAGLE-676 URL: https://issues.apache.org/jira/browse/EAGLE-676 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 Package hadoop jmx metric collector into eagle pacakge -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-650) Hadoop JMX Metric Monitoring Application
[ https://issues.apache.org/jira/browse/EAGLE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-650. Resolution: Fixed > Hadoop JMX Metric Monitoring Application > > > Key: EAGLE-650 > URL: https://issues.apache.org/jira/browse/EAGLE-650 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > Hadoop JMX Monitoring Application > * Hadoop Namenode JMX > * Hadoop Resource Manager JMX -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-665) Refactor kafka stream sink and hdfs audit topology using shuffle grouping
[ https://issues.apache.org/jira/browse/EAGLE-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-665. Resolution: Fixed > Refactor kafka stream sink and hdfs audit topology using shuffle grouping > - > > Key: EAGLE-665 > URL: https://issues.apache.org/jira/browse/EAGLE-665 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > Refactor kafka stream sink and hdfs audit topology using shuffle grouping -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-669) Investigate eagle app metric system referring to https://github.com/ooyala/metrics_storm
Hao Chen created EAGLE-669: -- Summary: Investigate eagle app metric system referring to https://github.com/ooyala/metrics_storm Key: EAGLE-669 URL: https://issues.apache.org/jira/browse/EAGLE-669 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Priority: Trivial Fix For: v0.5.0 Investigate eagle app metric system referring to https://github.com/ooyala/metrics_storm -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-668) Support properties type in text area instead input field of configuration
Hao Chen created EAGLE-668: -- Summary: Support properties type in text area instead input field of configuration Key: EAGLE-668 URL: https://issues.apache.org/jira/browse/EAGLE-668 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-665) Refactor kafka stream sink and hdfs audit topology using shuffle grouping
Hao Chen created EAGLE-665: -- Summary: Refactor kafka stream sink and hdfs audit topology using shuffle grouping Key: EAGLE-665 URL: https://issues.apache.org/jira/browse/EAGLE-665 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 Refactor kafka stream sink and hdfs audit topology using shuffle grouping -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-664) Add directly updating status API to rigger update status immediately
[ https://issues.apache.org/jira/browse/EAGLE-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-664: --- Assignee: Jilin, Jiang (was: Hao Chen) > Add directly updating status API to rigger update status immediately > > > Key: EAGLE-664 > URL: https://issues.apache.org/jira/browse/EAGLE-664 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Jilin, Jiang > Fix For: v0.5.0 > > > Add directly updating status API to rigger update status immediately, and > integrate with "refresh" button in front-end -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-664) Add directly updating status API to rigger update status immediately
Hao Chen created EAGLE-664: -- Summary: Add directly updating status API to rigger update status immediately Key: EAGLE-664 URL: https://issues.apache.org/jira/browse/EAGLE-664 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 Add directly updating status API to rigger update status immediately, and integrate with "refresh" button in front-end -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-663) Build git head COMMITID into eagle package and display in web page aside eagle version
[
https://issues.apache.org/jira/browse/EAGLE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-663:
---
Affects Version/s: v0.5.0
Fix Version/s: v0.5.0
> Build git head COMMITID into eagle package and display in web page aside
> eagle version
> --
>
> Key: EAGLE-663
> URL: https://issues.apache.org/jira/browse/EAGLE-663
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> {code}
> # Get git-head commit ID
> COMMITID=`git rev-parse HEAD`
> # Get current maven version
> VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}'
> --non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
> DATE=`date`
> # Generate
> classes/assets/build-version.json
> # Access as static resource
> /build-version.json
> {
> version: "$VERSION"
> commit: "$COMMITID"
> built: "$, MacOSX, 1.8.0_74-b02"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-663) Build git head COMMITID into eagle package and display in web page aside eagle version
[
https://issues.apache.org/jira/browse/EAGLE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-663:
---
Description:
{code}
# Get git-head commit ID
COMMITID=`git rev-parse HEAD`
# Get current maven version
VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}'
--non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
DATE=`date`
# Generate
classes/assets/build-version.json
# Access as static resource
/build-version.json
{
version: "$VERSION"
commit: "$COMMITID"
built: "$, MacOSX, 1.8.0_74-b02"
}
{code}
was:
{code}
# Get git-head commit ID
COMMITID=`git rev-parse HEAD`
# Get current maven version
VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}'
--non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
DATE=`date`
# Generate
classes/assets/build-version.json
# Access as static resource
/build-version.json
{
version: "$VERSION"
commit: "$COMMITID"
compiled: "$DATE, MacOSX, 1.8.0_74-b02"
}
{code}
> Build git head COMMITID into eagle package and display in web page aside
> eagle version
> --
>
> Key: EAGLE-663
> URL: https://issues.apache.org/jira/browse/EAGLE-663
> Project: Eagle
> Issue Type: Bug
>Reporter: Hao Chen
>Assignee: Hao Chen
>
> {code}
> # Get git-head commit ID
> COMMITID=`git rev-parse HEAD`
> # Get current maven version
> VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}'
> --non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
> DATE=`date`
> # Generate
> classes/assets/build-version.json
> # Access as static resource
> /build-version.json
> {
> version: "$VERSION"
> commit: "$COMMITID"
> built: "$, MacOSX, 1.8.0_74-b02"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (EAGLE-663) Build git head COMMITID into eagle package and display in web page aside eagle version
Hao Chen created EAGLE-663:
--
Summary: Build git head COMMITID into eagle package and display in
web page aside eagle version
Key: EAGLE-663
URL: https://issues.apache.org/jira/browse/EAGLE-663
Project: Eagle
Issue Type: Bug
Reporter: Hao Chen
Assignee: Hao Chen
{code}
# Get git-head commit ID
COMMITID=`git rev-parse HEAD`
# Get current maven version
VERSION=`mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}'
--non-recursive org.codehaus.mojo:exec-maven-plugin:1.3.1:exec`
DATE=`date`
# Generate
classes/assets/build-version.json
# Access as static resource
/build-version.json
{
version: "$VERSION"
commit: "$COMMITID"
date: "$DATE"
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-661) Status is wrongly shown as "INITIALIZED" when updating installed app's configuration
[ https://issues.apache.org/jira/browse/EAGLE-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-661: --- Assignee: Jilin, Jiang (was: Hao Chen) > Status is wrongly shown as "INITIALIZED" when updating installed app's > configuration > > > Key: EAGLE-661 > URL: https://issues.apache.org/jira/browse/EAGLE-661 > Project: Eagle > Issue Type: Bug >Reporter: Hao Chen >Assignee: Jilin, Jiang > Fix For: v0.5.0 > > > * Status is wrongly shown as "INITIALIZED" when updating installed app's > configuration > * Should use "Save" instead of "Install" button when updating installed app's > configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-661) Status is wrongly shown as "INITIALIZED" when updating installed app's configuration
[ https://issues.apache.org/jira/browse/EAGLE-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-661: --- Description: * Status is wrongly shown as "INITIALIZED" when updating installed app's configuration * Should use "Save" instead of "Install" button when updating installed app's configuration was:Status is wrongly shown as "INITIALIZED" when updating installed app's configuration > Status is wrongly shown as "INITIALIZED" when updating installed app's > configuration > > > Key: EAGLE-661 > URL: https://issues.apache.org/jira/browse/EAGLE-661 > Project: Eagle > Issue Type: Bug >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > * Status is wrongly shown as "INITIALIZED" when updating installed app's > configuration > * Should use "Save" instead of "Install" button when updating installed app's > configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-661) Status is wrongly shown as "INITIALIZED" when updating installed app's configuration
Hao Chen created EAGLE-661: -- Summary: Status is wrongly shown as "INITIALIZED" when updating installed app's configuration Key: EAGLE-661 URL: https://issues.apache.org/jira/browse/EAGLE-661 Project: Eagle Issue Type: Bug Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 Status is wrongly shown as "INITIALIZED" when updating installed app's configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-652) services health check for hdfs,hbase and yarn
[ https://issues.apache.org/jira/browse/EAGLE-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15593761#comment-15593761 ] Hao Chen commented on EAGLE-652: @yulu Could you please assign the ticket to yourself? > services health check for hdfs,hbase and yarn > - > > Key: EAGLE-652 > URL: https://issues.apache.org/jira/browse/EAGLE-652 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: yupu > Labels: features > > The app aims to monitor those services with a master-slave structured > topology, and provides metrics at the HOST level. Specifically, this app will > support the following services healthy check > •HDFS: namenode, datanode, journalnode > •HBASE: hmaster, regionservers > YARN: resourcemanager, nodemanagers, historyserver -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-658) Add reserved "global" siteId as shared namespace
Hao Chen created EAGLE-658: -- Summary: Add reserved "global" siteId as shared namespace Key: EAGLE-658 URL: https://issues.apache.org/jira/browse/EAGLE-658 Project: Eagle Issue Type: New Feature Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-657) EagleServiceMetricSink
Hao Chen created EAGLE-657:
--
Summary: EagleServiceMetricSink
Key: EAGLE-657
URL: https://issues.apache.org/jira/browse/EAGLE-657
Project: Eagle
Issue Type: New Feature
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
Fix For: v0.5.0
Persist metric to eagle metric store
{code}
{
metric {
enabled: true
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-657) EagleServiceMetricSink
[
https://issues.apache.org/jira/browse/EAGLE-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-657:
---
Description:
Persist metric to eagle metric store
{code}
{
metric {
enable: true
}
}
{code}
was:
Persist metric to eagle metric store
{code}
{
metric {
enabled: true
}
}
{code}
> EagleServiceMetricSink
> --
>
> Key: EAGLE-657
> URL: https://issues.apache.org/jira/browse/EAGLE-657
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Persist metric to eagle metric store
> {code}
> {
> metric {
>enable: true
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-651) HBase JMX Metric Monitoring Application
[ https://issues.apache.org/jira/browse/EAGLE-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-651: --- Description: HBase Master JMX Monitoring HBase Region Server Jmx Monitoring was:HBase Master JMX Monitoring > HBase JMX Metric Monitoring Application > --- > > Key: EAGLE-651 > URL: https://issues.apache.org/jira/browse/EAGLE-651 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > HBase Master JMX Monitoring > HBase Region Server Jmx Monitoring -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-651) HBase JMX Metric Monitoring Application
[ https://issues.apache.org/jira/browse/EAGLE-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-651: --- Description: HBase Master JMX Monitoring (was: HBase Master JMX Monitoring HBase Region Server Jmx Monitoring) > HBase JMX Metric Monitoring Application > --- > > Key: EAGLE-651 > URL: https://issues.apache.org/jira/browse/EAGLE-651 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > HBase Master JMX Monitoring -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-651) HBase JMX Metric Monitoring Application
Hao Chen created EAGLE-651: -- Summary: HBase JMX Metric Monitoring Application Key: EAGLE-651 URL: https://issues.apache.org/jira/browse/EAGLE-651 Project: Eagle Issue Type: New Feature Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 HBase Master JMX Monitoring -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-650) Hadoop JMX Metric Monitoring Application
[ https://issues.apache.org/jira/browse/EAGLE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-650: --- Summary: Hadoop JMX Metric Monitoring Application (was: Hadoop JMX Monitoring Application) > Hadoop JMX Metric Monitoring Application > > > Key: EAGLE-650 > URL: https://issues.apache.org/jira/browse/EAGLE-650 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > Hadoop JMX Monitoring Application > * Hadoop Namenode JMX > * Hadoop Resource Manager JMX -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-650) Hadoop JMX Monitoring Application
Hao Chen created EAGLE-650: -- Summary: Hadoop JMX Monitoring Application Key: EAGLE-650 URL: https://issues.apache.org/jira/browse/EAGLE-650 Project: Eagle Issue Type: New Feature Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 Hadoop JMX Monitoring Application * Hadoop Namenode JMX * Hadoop Resource Manager JMX -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-647) Support Policy Execution Interpreter and Planner to compile siddhi query to distributed execution plan
[ https://issues.apache.org/jira/browse/EAGLE-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-647: --- Issue Type: Improvement (was: Bug) > Support Policy Execution Interpreter and Planner to compile siddhi query to > distributed execution plan > -- > > Key: EAGLE-647 > URL: https://issues.apache.org/jira/browse/EAGLE-647 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > Support Policy Execution Interpreter and Planner to compile siddhi query to > distributed execution plan > * Support parse siddhi pattern and join query as distributed execution > * Support alias in inner join condition > * Refactor PolicyIntepreter to eagle-alert-engine and decoupel > PolicyExecutionPlanner > * Fix factory method for PolicyExecutionPlanner -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-647) Support Policy Execution Interpreter and Planner to compile siddhi query to distributed execution plan
Hao Chen created EAGLE-647: -- Summary: Support Policy Execution Interpreter and Planner to compile siddhi query to distributed execution plan Key: EAGLE-647 URL: https://issues.apache.org/jira/browse/EAGLE-647 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 Support Policy Execution Interpreter and Planner to compile siddhi query to distributed execution plan * Support parse siddhi pattern and join query as distributed execution * Support alias in inner join condition * Refactor PolicyIntepreter to eagle-alert-engine and decoupel PolicyExecutionPlanner * Fix factory method for PolicyExecutionPlanner -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-639) Generate sortSpec only on externalWindow
Hao Chen created EAGLE-639: -- Summary: Generate sortSpec only on externalWindow Key: EAGLE-639 URL: https://issues.apache.org/jira/browse/EAGLE-639 Project: Eagle Issue Type: Sub-task Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 Generate sortSpec only on externalWindow -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-635) Refactor policy parser and validator for richer plan details and better performance
[
https://issues.apache.org/jira/browse/EAGLE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-635:
---
Description:
h2. Changes
* Refactor policy parser and validator for richer plan details and better
performance
* Decouple PolicyExecutionPlan and PolicyValidation
h2. API
* Parse API
{code}
POST /metadata/policies/parse
Accept-Type: text
from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd,
user, count() as total_count group by cmd,user insert into
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
{code}
* Validation API
{code}
POST /metadata/policies/validate
Accept-Type: application/json
{
"name": "hdfsPolicy",
"description": "hdfsPolicy",
"inputStreams": [
"HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
],
"outputStreams": [
"HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
],
"definition": {
"type": "siddhi",
"value": "from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2
min) select cmd, user, count() as total_count group by cmd,user insert into
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
},
"partitionSpec": [
{
"streamId": "hdfs_audit_log_enriched_stream",
"type": "GROUPBY",
"columns" : [
"cmd"
]
}
],
"parallelismHint": 2
}
{code}
h2. Use Cases
* *parse*: could continuously call `parse` API aside during user keeps typing
to verify the syntax and automatically generate input/output/partition , as it
won't call back-end db, so will be very fast.
* *validate*: when user finishes defining policy, the api will validate the
metadata end2end
was:
h2. Changes
* Refactor policy parser and validator for richer plan details and better
performance
* Decouple PolicyExecutionPlan and PolicyValidation
h2. API
* Parse API
{code}
POST /metadata/policies/parse
Accept-Type: text
from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd,
user, count() as total_count group by cmd,user insert into
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
{code}
* Validation API
{code}
POST /metadata/policies/validate
Accept-Type: application/json
{
"name": "hdfsPolicy",
"description": "hdfsPolicy",
"inputStreams": [
"HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
],
"outputStreams": [
"HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
],
"definition": {
"type": "siddhi",
"value": "from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2
min) select cmd, user, count() as total_count group by cmd,user insert into
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
},
"partitionSpec": [
{
"streamId": "hdfs_audit_log_enriched_stream",
"type": "GROUPBY",
"columns" : [
"cmd"
]
}
],
"parallelismHint": 2
}
{code}
h2. Use Cases
* **parse**: So you could continuously call `parse` API aside during user keeps
typing to verify the syntax and automatically generate input/output/partition ,
as it won't call back-end db, so will be very fast.
* **validate**: when user finishes defining policy, the api will validate the
metadata end2end
> Refactor policy parser and validator for richer plan details and better
> performance
> ---
>
> Key: EAGLE-635
> URL: https://issues.apache.org/jira/browse/EAGLE-635
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> h2. Changes
> * Refactor policy parser and validator for richer plan details and better
> performance
> * Decouple PolicyExecutionPlan and PolicyValidation
> h2. API
> * Parse API
> {code}
> POST /metadata/policies/parse
> Accept-Type: text
> from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select
> cmd, user, count() as total_count group by cmd,user insert into
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
> {code}
> * Validation API
> {code}
> POST /metadata/policies/validate
> Accept-Type: application/json
> {
>"name": "hdfsPolicy",
>"description": "hdfsPolicy",
>"inputStreams": [
> "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
>],
>"outputStreams": [
> "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
>],
>"definition": {
> "type": "siddhi",
> "value": "from
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd,
> user, count() as total_count group by cmd,user insert into
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
>},
>"partitionSpec": [
> {
> "streamId": "hdfs_audit_log_enriched_stream",
> "type": "GROUPBY",
> "columns" : [
> "cmd"
> ]
> }
>],
>"parallelismHint": 2
> }
> {code}
> h2. Use Cases
> *
[jira] [Updated] (EAGLE-635) Refactor policy parser and validator for richer plan details and better performance
[
https://issues.apache.org/jira/browse/EAGLE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-635:
---
Description:
h2. Changes
* Refactor policy parser and validator for richer plan details and better
performance
* Decouple PolicyExecutionPlan and PolicyValidation
h2. API
* Parse API
{code}
POST /metadata/policies/parse
Accept-Type: text
from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd,
user, count() as total_count group by cmd,user insert into
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
{code}
* Validation API
{code}
POST /metadata/policies/validate
Accept-Type: application/json
{
"name": "hdfsPolicy",
"description": "hdfsPolicy",
"inputStreams": [
"HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
],
"outputStreams": [
"HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
],
"definition": {
"type": "siddhi",
"value": "from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2
min) select cmd, user, count() as total_count group by cmd,user insert into
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
},
"partitionSpec": [
{
"streamId": "hdfs_audit_log_enriched_stream",
"type": "GROUPBY",
"columns" : [
"cmd"
]
}
],
"parallelismHint": 2
}
{code}
h2. Use Cases
* **parse**: So you could continuously call `parse` API aside during user keeps
typing to verify the syntax and automatically generate input/output/partition ,
as it won't call back-end db, so will be very fast.
* **validate**: when user finishes defining policy, the api will validate the
metadata end2end
was:
h2. Changes
* Refactor policy parser and validator for richer plan details and better
performance
* Decouple PolicyExecutionPlan and PolicyValidation
h2. API
* Parse API
{code}
POST /metadata/policies/parse
Accept-Type: text
from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd,
user, count() as total_count group by cmd,user insert into
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
{code}
* Validation API
{code}
POST /metadata/policies/validate
Accept-Type: application/json
{
"name": "hdfsPolicy",
"description": "hdfsPolicy",
"inputStreams": [
"HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
],
"outputStreams": [
"HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
],
"definition": {
"type": "siddhi",
"value": "from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2
min) select cmd, user, count() as total_count group by cmd,user insert into
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
},
"partitionSpec": [
{
"streamId": "hdfs_audit_log_enriched_stream",
"type": "GROUPBY",
"columns" : [
"cmd"
]
}
],
"parallelismHint": 2
}
{code}
> Refactor policy parser and validator for richer plan details and better
> performance
> ---
>
> Key: EAGLE-635
> URL: https://issues.apache.org/jira/browse/EAGLE-635
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> h2. Changes
> * Refactor policy parser and validator for richer plan details and better
> performance
> * Decouple PolicyExecutionPlan and PolicyValidation
> h2. API
> * Parse API
> {code}
> POST /metadata/policies/parse
> Accept-Type: text
> from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select
> cmd, user, count() as total_count group by cmd,user insert into
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
> {code}
> * Validation API
> {code}
> POST /metadata/policies/validate
> Accept-Type: application/json
> {
>"name": "hdfsPolicy",
>"description": "hdfsPolicy",
>"inputStreams": [
> "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
>],
>"outputStreams": [
> "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
>],
>"definition": {
> "type": "siddhi",
> "value": "from
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd,
> user, count() as total_count group by cmd,user insert into
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
>},
>"partitionSpec": [
> {
> "streamId": "hdfs_audit_log_enriched_stream",
> "type": "GROUPBY",
> "columns" : [
> "cmd"
> ]
> }
>],
>"parallelismHint": 2
> }
> {code}
> h2. Use Cases
> * **parse**: So you could continuously call `parse` API aside during user
> keeps typing to verify the syntax and automatically generate
> input/output/partition , as it won't call back-end db, so will be very fast.
> * **validate**: when user finishes defining policy, the api will validate the
> metadata end2end
[jira] [Updated] (EAGLE-635) Refactor policy parser and validator for richer plan details and better performance
[
https://issues.apache.org/jira/browse/EAGLE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-635:
---
Description:
## Changes
* Refactor policy parser and validator for richer plan details and better
performance
* Decouple PolicyExecutionPlan and PolicyValidation
## API
* Parse API
{code}
POST /metadata/policies/parse
Accept-Type: text
from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd,
user, count() as total_count group by cmd,user insert into
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
{code}
* Validation API
{code}
POST /metadata/policies/validate
Accept-Type: application/json
{
"name": "hdfsPolicy",
"description": "hdfsPolicy",
"inputStreams": [
"HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
],
"outputStreams": [
"HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
],
"definition": {
"type": "siddhi",
"value": "from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2
min) select cmd, user, count() as total_count group by cmd,user insert into
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
},
"partitionSpec": [
{
"streamId": "hdfs_audit_log_enriched_stream",
"type": "GROUPBY",
"columns" : [
"cmd"
]
}
],
"parallelismHint": 2
}
{code}
was:
* Refactor policy parser and validator for richer plan details and better
performance
* Decouple PolicyExecutionPlan and PolicyValidation
> Refactor policy parser and validator for richer plan details and better
> performance
> ---
>
> Key: EAGLE-635
> URL: https://issues.apache.org/jira/browse/EAGLE-635
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> ## Changes
> * Refactor policy parser and validator for richer plan details and better
> performance
> * Decouple PolicyExecutionPlan and PolicyValidation
> ## API
> * Parse API
> {code}
> POST /metadata/policies/parse
> Accept-Type: text
> from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select
> cmd, user, count() as total_count group by cmd,user insert into
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
> {code}
> * Validation API
> {code}
> POST /metadata/policies/validate
> Accept-Type: application/json
> {
>"name": "hdfsPolicy",
>"description": "hdfsPolicy",
>"inputStreams": [
> "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
>],
>"outputStreams": [
> "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
>],
>"definition": {
> "type": "siddhi",
> "value": "from
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd,
> user, count() as total_count group by cmd,user insert into
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
>},
>"partitionSpec": [
> {
> "streamId": "hdfs_audit_log_enriched_stream",
> "type": "GROUPBY",
> "columns" : [
> "cmd"
> ]
> }
>],
>"parallelismHint": 2
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-635) Refactor policy parser and validator for richer plan details and better performance
[
https://issues.apache.org/jira/browse/EAGLE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-635:
---
Description:
h2. Changes
* Refactor policy parser and validator for richer plan details and better
performance
* Decouple PolicyExecutionPlan and PolicyValidation
h2. API
* Parse API
{code}
POST /metadata/policies/parse
Accept-Type: text
from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd,
user, count() as total_count group by cmd,user insert into
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
{code}
* Validation API
{code}
POST /metadata/policies/validate
Accept-Type: application/json
{
"name": "hdfsPolicy",
"description": "hdfsPolicy",
"inputStreams": [
"HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
],
"outputStreams": [
"HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
],
"definition": {
"type": "siddhi",
"value": "from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2
min) select cmd, user, count() as total_count group by cmd,user insert into
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
},
"partitionSpec": [
{
"streamId": "hdfs_audit_log_enriched_stream",
"type": "GROUPBY",
"columns" : [
"cmd"
]
}
],
"parallelismHint": 2
}
{code}
was:
## Changes
* Refactor policy parser and validator for richer plan details and better
performance
* Decouple PolicyExecutionPlan and PolicyValidation
## API
* Parse API
{code}
POST /metadata/policies/parse
Accept-Type: text
from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd,
user, count() as total_count group by cmd,user insert into
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
{code}
* Validation API
{code}
POST /metadata/policies/validate
Accept-Type: application/json
{
"name": "hdfsPolicy",
"description": "hdfsPolicy",
"inputStreams": [
"HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
],
"outputStreams": [
"HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
],
"definition": {
"type": "siddhi",
"value": "from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2
min) select cmd, user, count() as total_count group by cmd,user insert into
HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
},
"partitionSpec": [
{
"streamId": "hdfs_audit_log_enriched_stream",
"type": "GROUPBY",
"columns" : [
"cmd"
]
}
],
"parallelismHint": 2
}
{code}
> Refactor policy parser and validator for richer plan details and better
> performance
> ---
>
> Key: EAGLE-635
> URL: https://issues.apache.org/jira/browse/EAGLE-635
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> h2. Changes
> * Refactor policy parser and validator for richer plan details and better
> performance
> * Decouple PolicyExecutionPlan and PolicyValidation
> h2. API
> * Parse API
> {code}
> POST /metadata/policies/parse
> Accept-Type: text
> from HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select
> cmd, user, count() as total_count group by cmd,user insert into
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
> {code}
> * Validation API
> {code}
> POST /metadata/policies/validate
> Accept-Type: application/json
> {
>"name": "hdfsPolicy",
>"description": "hdfsPolicy",
>"inputStreams": [
> "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX"
>],
>"outputStreams": [
> "HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT"
>],
>"definition": {
> "type": "siddhi",
> "value": "from
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX#window.timeBatch(2 min) select cmd,
> user, count() as total_count group by cmd,user insert into
> HDFS_AUDIT_LOG_ENRICHED_STREAM_SANDBOX_OUT "
>},
>"partitionSpec": [
> {
> "streamId": "hdfs_audit_log_enriched_stream",
> "type": "GROUPBY",
> "columns" : [
> "cmd"
> ]
> }
>],
>"parallelismHint": 2
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-635) Refactor policy parser and validator for richer plan details and better performance
[ https://issues.apache.org/jira/browse/EAGLE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-635: --- Issue Type: Improvement (was: Bug) > Refactor policy parser and validator for richer plan details and better > performance > --- > > Key: EAGLE-635 > URL: https://issues.apache.org/jira/browse/EAGLE-635 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > * Refactor policy parser and validator for richer plan details and better > performance > * Decouple PolicyExecutionPlan and PolicyValidation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-635) Refactor policy parser and validator for richer plan details and better performance
Hao Chen created EAGLE-635: -- Summary: Refactor policy parser and validator for richer plan details and better performance Key: EAGLE-635 URL: https://issues.apache.org/jira/browse/EAGLE-635 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 * Refactor policy parser and validator for richer plan details and better performance * Decouple PolicyExecutionPlan and PolicyValidation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-627) Add PolicyValidator and Validation API
[
https://issues.apache.org/jira/browse/EAGLE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-627:
---
Description:
Add Policy PolicyValidator and Validation API on
* Validate SiddhiQL syntax problem
* Provide Internal information like:
* Validate syntax is ok
* Explain details like inputStreams and outputStreams
API:
{code}
POST /metadata/policies/validate
Request: PolicyDefinition
Response: PolicyValidation
{code}
Reference:
*
https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert-parent/eagle-alert/alert-common/src/main/java/org/apache/eagle/alert/engine/coordinator/PolicyDefinition.java
*
https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert-parent/eagle-alert/alert-metadata-parent/alert-metadata-service/src/main/java/org/apache/eagle/service/metadata/resource/PolicyValidation.java
was:
Add Policy PolicyValidator and Validation API on
* Validate SiddhiQL syntax problem
* Provide Internal information like:
* Validate syntax is ok
* Explain details like inputStreams and outputStreams
API:
{code}
POST /metadata/policies/validate
Request: PolicyDefinition
Response: PolicyValidation
{code}
> Add PolicyValidator and Validation API
> --
>
> Key: EAGLE-627
> URL: https://issues.apache.org/jira/browse/EAGLE-627
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Add Policy PolicyValidator and Validation API on
> * Validate SiddhiQL syntax problem
> * Provide Internal information like:
> * Validate syntax is ok
> * Explain details like inputStreams and outputStreams
> API:
> {code}
> POST /metadata/policies/validate
> Request: PolicyDefinition
> Response: PolicyValidation
> {code}
> Reference:
> *
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert-parent/eagle-alert/alert-common/src/main/java/org/apache/eagle/alert/engine/coordinator/PolicyDefinition.java
> *
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert-parent/eagle-alert/alert-metadata-parent/alert-metadata-service/src/main/java/org/apache/eagle/service/metadata/resource/PolicyValidation.java
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-627) Add PolicyValidator and Validation API
[
https://issues.apache.org/jira/browse/EAGLE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-627:
---
Description:
Add Policy PolicyValidator and Validation API on
* Validate SiddhiQL syntax problem
* Provide Internal information like:
* Validate syntax is ok
* Explain details like inputStreams and outputStreams
API:
{code}
POST /metadata/policies/validate
Request: PolicyDefinition
Response: PolicyValidation
{code}
was:
Add Policy PolicyValidator and Validation API on
* Validate SiddhiQL syntax problem
* Provide Internal information like:
* Validate syntax is ok
* Explain details like inputStreams and outputStreams
API:
{code}
POST /metadata/policies/validate
Request: PolicyDefinition
{code}
> Add PolicyValidator and Validation API
> --
>
> Key: EAGLE-627
> URL: https://issues.apache.org/jira/browse/EAGLE-627
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Add Policy PolicyValidator and Validation API on
> * Validate SiddhiQL syntax problem
> * Provide Internal information like:
> * Validate syntax is ok
> * Explain details like inputStreams and outputStreams
> API:
> {code}
> POST /metadata/policies/validate
> Request: PolicyDefinition
> Response: PolicyValidation
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-627) Add PolicyValidator and Validation API
[
https://issues.apache.org/jira/browse/EAGLE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-627:
---
Description:
Add Policy PolicyValidator and Validation API on
* Validate SiddhiQL syntax problem
* Provide Internal information like:
* Validate syntax is ok
* Explain details like inputStreams and outputStreams
API:
{code}
POST /metadata/policies/validate
Request: PolicyDefinition
{code}
was:
Add Policy PolicyValidator and Validation API on
* Validate SiddhiQL syntax problem
* Provide Internal information like:
* Validate syntax is ok
* Explain details like inputStreams and outputStreams
API:
{code}
POST /metadata/policies/validate
{code}
> Add PolicyValidator and Validation API
> --
>
> Key: EAGLE-627
> URL: https://issues.apache.org/jira/browse/EAGLE-627
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Add Policy PolicyValidator and Validation API on
> * Validate SiddhiQL syntax problem
> * Provide Internal information like:
> * Validate syntax is ok
> * Explain details like inputStreams and outputStreams
> API:
> {code}
> POST /metadata/policies/validate
> Request: PolicyDefinition
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-630) Add Publishments to Policy API
[
https://issues.apache.org/jira/browse/EAGLE-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-630:
---
Labels: alert-service (was: )
> Add Publishments to Policy API
> --
>
> Key: EAGLE-630
> URL: https://issues.apache.org/jira/browse/EAGLE-630
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Labels: alert-service
> Fix For: v0.5.0
>
>
> Path:
> {code}
> POST /metadata/policies/{policyId}/publishments/
> {code}
> Data: String array, like:
> {code}
> [
>"publishmentName1", "publishmentName2",.., "publishmentNameN"
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (EAGLE-630) Add Publishments to Policy API
[
https://issues.apache.org/jira/browse/EAGLE-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen resolved EAGLE-630.
Resolution: Fixed
> Add Publishments to Policy API
> --
>
> Key: EAGLE-630
> URL: https://issues.apache.org/jira/browse/EAGLE-630
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Labels: alert-service
> Fix For: v0.5.0
>
>
> Path:
> {code}
> POST /metadata/policies/{policyId}/publishments/
> {code}
> Data: String array, like:
> {code}
> [
>"publishmentName1", "publishmentName2",.., "publishmentNameN"
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EAGLE-630) Add Publishments to Policy API
[
https://issues.apache.org/jira/browse/EAGLE-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15581298#comment-15581298
]
Hao Chen commented on EAGLE-630:
[~smith3816]
> Add Publishments to Policy API
> --
>
> Key: EAGLE-630
> URL: https://issues.apache.org/jira/browse/EAGLE-630
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Path:
> {code}
> POST /metadata/policies/{policyId}/publishments/
> {code}
> Data: String array, like:
> {code}
> [
>"publishmentName1", "publishmentName2",.., "publishmentNameN"
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (EAGLE-630) Add Publishments to Policy API
Hao Chen created EAGLE-630:
--
Summary: Add Publishments to Policy API
Key: EAGLE-630
URL: https://issues.apache.org/jira/browse/EAGLE-630
Project: Eagle
Issue Type: New Feature
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
Fix For: v0.5.0
Path:
{code}
POST /metadata/policies/{policyId}/publishments/
{code}
Data: String array, like:
{code}
[
"publishmentName1", "publishmentName2",.., "publishmentNameN"
]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (EAGLE-627) Add PolicyValidator and Validation API
[
https://issues.apache.org/jira/browse/EAGLE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen resolved EAGLE-627.
Resolution: Fixed
> Add PolicyValidator and Validation API
> --
>
> Key: EAGLE-627
> URL: https://issues.apache.org/jira/browse/EAGLE-627
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Add Policy PolicyValidator and Validation API on
> * Validate SiddhiQL syntax problem
> * Provide Internal information like:
> * Validate syntax is ok
> * Explain details like inputStreams and outputStreams
> API:
> {code}
> POST /metadata/policies/validate
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-627) Add PolicyValidator and Validation API
[
https://issues.apache.org/jira/browse/EAGLE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-627:
---
Summary: Add PolicyValidator and Validation API (was: Add Policy
PolicyValidator and Validation API)
> Add PolicyValidator and Validation API
> --
>
> Key: EAGLE-627
> URL: https://issues.apache.org/jira/browse/EAGLE-627
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Add Policy PolicyValidator and Validation API on
> * Validate SiddhiQL syntax problem
> * Provide Internal information like:
> * Validate syntax is ok
> * Explain details like inputStreams and outputStreams
> API:
> {code}
> POST /metadata/policies/validate
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-627) Add Policy PolicyValidator and Validation API
[
https://issues.apache.org/jira/browse/EAGLE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-627:
---
Description:
Add Policy PolicyValidator and Validation API on
* Validate SiddhiQL syntax problem
* Provide Internal information like:
* Validate syntax is ok
* Explain details like inputStreams and outputStreams
API:
{code}
POST /metadata/policies/validate
{code}
was:
Add Policy SiddhiQL Explain API to:
* Validate SiddhiQL syntax problem
* Provide Internal information like:
* Validate syntax is ok
* Explain details like inputStreams and outputStreams
> Add Policy PolicyValidator and Validation API
> -
>
> Key: EAGLE-627
> URL: https://issues.apache.org/jira/browse/EAGLE-627
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Add Policy PolicyValidator and Validation API on
> * Validate SiddhiQL syntax problem
> * Provide Internal information like:
> * Validate syntax is ok
> * Explain details like inputStreams and outputStreams
> API:
> {code}
> POST /metadata/policies/validate
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-627) Add Policy PolicyValidator and Validation API
[ https://issues.apache.org/jira/browse/EAGLE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-627: --- Summary: Add Policy PolicyValidator and Validation API (was: Add Policy SiddhiQL Explain API) > Add Policy PolicyValidator and Validation API > - > > Key: EAGLE-627 > URL: https://issues.apache.org/jira/browse/EAGLE-627 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > Add Policy SiddhiQL Explain API to: > * Validate SiddhiQL syntax problem > * Provide Internal information like: > * Validate syntax is ok > * Explain details like inputStreams and outputStreams -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-627) Add Policy SiddhiQL Explain API
Hao Chen created EAGLE-627: -- Summary: Add Policy SiddhiQL Explain API Key: EAGLE-627 URL: https://issues.apache.org/jira/browse/EAGLE-627 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 Add Policy SiddhiQL Explain API to: * Validate SiddhiQL syntax problem * Provide Internal information like: * Validate syntax is ok * Explain details like inputStreams and outputStreams -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-626) Add Eagle HBase Metric Store Publisher
Hao Chen created EAGLE-626: -- Summary: Add Eagle HBase Metric Store Publisher Key: EAGLE-626 URL: https://issues.apache.org/jira/browse/EAGLE-626 Project: Eagle Issue Type: New Feature Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-625) Site home page error for missing partials/site/home.html
Hao Chen created EAGLE-625:
--
Summary: Site home page error for missing partials/site/home.html
Key: EAGLE-625
URL: https://issues.apache.org/jira/browse/EAGLE-625
Project: Eagle
Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Jilin, Jiang
Fix For: v0.5.0
{code}
url:
partials/site/home.html?_=0.5842998691423007
status:
404
exception:
undefined
message:
undefined
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-624) Installation Doc is not correctly shown in Installation Dialog
[ https://issues.apache.org/jira/browse/EAGLE-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-624: --- Description: h2. Improvements * Show dependencies apps number * Support XML child node tree as String in app docs * Cleanup eagle-server dependencies and output * Move business logic specific logics into dev profile * Rename header and remove pre fo installation content h2. Bugs * Fix siteName bug in ui * Installation Doc is not correctly shown in Installation Dialog was:Installation Doc is not correctly shown in Installation Dialog > Installation Doc is not correctly shown in Installation Dialog > -- > > Key: EAGLE-624 > URL: https://issues.apache.org/jira/browse/EAGLE-624 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Labels: eagle-ui > Fix For: v0.5.0 > > > h2. Improvements > * Show dependencies apps number > * Support XML child node tree as String in app docs > * Cleanup eagle-server dependencies and output > * Move business logic specific logics into dev profile > * Rename header and remove pre fo installation content > h2. Bugs > * Fix siteName bug in ui > * Installation Doc is not correctly shown in Installation Dialog -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-624) Installation Doc is not correctly shown in Installation Dialog
[ https://issues.apache.org/jira/browse/EAGLE-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-624: --- Labels: eagle-ui (was: ) > Installation Doc is not correctly shown in Installation Dialog > -- > > Key: EAGLE-624 > URL: https://issues.apache.org/jira/browse/EAGLE-624 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Labels: eagle-ui > Fix For: v0.5.0 > > > Installation Doc is not correctly shown in Installation Dialog -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (EAGLE-624) Installation Doc is not correctly shown in Installation Dialog
[ https://issues.apache.org/jira/browse/EAGLE-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen reassigned EAGLE-624: -- Assignee: Hao Chen (was: Jilin, Jiang) > Installation Doc is not correctly shown in Installation Dialog > -- > > Key: EAGLE-624 > URL: https://issues.apache.org/jira/browse/EAGLE-624 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > Installation Doc is not correctly shown in Installation Dialog -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-624) Installation Doc is not correctly shown in Installation Dialog
Hao Chen created EAGLE-624: -- Summary: Installation Doc is not correctly shown in Installation Dialog Key: EAGLE-624 URL: https://issues.apache.org/jira/browse/EAGLE-624 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Jilin, Jiang Fix For: v0.5.0 Installation Doc is not correctly shown in Installation Dialog -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-623) [Maven] Move dependencies in profile "dev" to "eagle-topology-assembly"
Hao Chen created EAGLE-623: -- Summary: [Maven] Move dependencies in profile "dev" to "eagle-topology-assembly" Key: EAGLE-623 URL: https://issues.apache.org/jira/browse/EAGLE-623 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: wujinhu Fix For: v0.5.0 "dev" profile is just to make sure developer could easily load all apps in development mode. So we should move all application-specific dependencies into "eagle-topology-assembly" and let "eagle-server" depend on "eagle-topology-assembly" in "dev" profile, and always keep "eagle-topology-assembly" as single source of truth to assemble different applications' topologies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-619) UI Home display site states
[ https://issues.apache.org/jira/browse/EAGLE-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-619: --- Description: UI Home display site states > UI Home display site states > --- > > Key: EAGLE-619 > URL: https://issues.apache.org/jira/browse/EAGLE-619 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > Fix For: v0.5.0 > > > UI Home display site states -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-613) Support modify ApplicationEntity through POST /rest/apps/{UUID}/
[
https://issues.apache.org/jira/browse/EAGLE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-613:
---
Description:
Support modify ApplicationEntity through
{code}
POST /rest/apps/{UUID}/
{code}
* REQUEST BODY*
ApplicationEntity (without streams)
was:
Support modify ApplicationEntity through
{code}
POST /rest/apps/{UUID}/
{code}
> Support modify ApplicationEntity through POST /rest/apps/{UUID}/
>
>
> Key: EAGLE-613
> URL: https://issues.apache.org/jira/browse/EAGLE-613
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Support modify ApplicationEntity through
> {code}
> POST /rest/apps/{UUID}/
> {code}
> * REQUEST BODY*
> ApplicationEntity (without streams)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
