RE: wish team prefect the doc
Hi, Caoyu, Recently I tested Eagle 0.4.0 on cloudera (CDH5.5.2), and wrote a doc for deploying apache Eagle on CDH here : https://github.com/DadanielZ/eaglemonitoring.github.io/blob/master/cloudera-integration.md @eagle-team Also I opened a pull request for this doc to repository: “eaglemonitoring.github.io”, but I do not have write access to it, can anyone review it ? Thanks and regards, Da From: caoyu03 [mailto:caoy...@sinoiov.com] Sent: Sunday, July 24, 2016 8:45 PM To: devSubject: wish team prefect the doc HI eagle dev: I wish use eagle to our product cluster .now,im study it in CDH test cluster. But the doc guide for sandbox. I wish the doc wirte for CDH or apache hadoop. and the doc is not good . it too simple. please prefect logical structure. some bug: 1. Step 4: Submit topologies # start HDFS audilt log monitoring $ bin/eagle-topology.sh --main eagle.security.auditlog.HdfsAuditLogProcessorMain --config conf/-hdfsAuditLog-application.conf start --main eagle.security.auditlog.HdfsAuditLogProcessorMain need change to --main org.apache.eagle.security.auditlog.HdfsAuditLogProcessorMain —-topology {xxx-topology-name} 2. [cid:6593BD176F8CCB8ED5F5B34EC1B5CF4D] in my deploy eagle is can see the setup button.my eagle is look like this: [cid:C5BDCDFAFA717EC6AA8E554F21062636] it’s version differ ? tks. english is not good .
[jira] [Created] (EAGLE-397) Implement KafkaStreamSink with type safe StreamSinkContext
Hao Chen created EAGLE-397: -- Summary: Implement KafkaStreamSink with type safe StreamSinkContext Key: EAGLE-397 URL: https://issues.apache.org/jira/browse/EAGLE-397 Project: Eagle Issue Type: Sub-task Reporter: Hao Chen -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (EAGLE-395) Doc mismatch package name
[ https://issues.apache.org/jira/browse/EAGLE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393513#comment-15393513 ] Michael Wu edited comment on EAGLE-395 at 7/26/16 9:31 AM: --- As we have refactored the site pages, the following page should be verified: tutorial/userprofile.html hbase-data-activity-monitoring.html was (Author: wuziyang): tutorial/userprofile.html hbase-data-activity-monitoring.html > Doc mismatch package name > - > > Key: EAGLE-395 > URL: https://issues.apache.org/jira/browse/EAGLE-395 > Project: Eagle > Issue Type: Bug >Reporter: Su Ralph >Assignee: Michael Wu > Fix For: v0.5.0 > > > From Caoyu3: > 1.Step 4: Submit topologies > # start HDFS audilt log monitoring > $ bin/eagle-topology.sh --main > eagle.security.auditlog.HdfsAuditLogProcessorMain --config > conf/-hdfsAuditLog-application.conf start > --main eagle.security.auditlog.HdfsAuditLogProcessorMain need change > to --main org.apache.eagle.security.auditlog.HdfsAuditLogProcessorMain > —-topology {xxx-topology-name} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-395) Doc mismatch package name
[ https://issues.apache.org/jira/browse/EAGLE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393513#comment-15393513 ] Michael Wu commented on EAGLE-395: -- tutorial/userprofile.html hbase-data-activity-monitoring.html > Doc mismatch package name > - > > Key: EAGLE-395 > URL: https://issues.apache.org/jira/browse/EAGLE-395 > Project: Eagle > Issue Type: Bug >Reporter: Su Ralph >Assignee: Michael Wu > Fix For: v0.5.0 > > > From Caoyu3: > 1.Step 4: Submit topologies > # start HDFS audilt log monitoring > $ bin/eagle-topology.sh --main > eagle.security.auditlog.HdfsAuditLogProcessorMain --config > conf/-hdfsAuditLog-application.conf start > --main eagle.security.auditlog.HdfsAuditLogProcessorMain need change > to --main org.apache.eagle.security.auditlog.HdfsAuditLogProcessorMain > —-topology {xxx-topology-name} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: wish team prefect the doc
@caoyu03, 1. The package name of the class HdfsAuditLogProcessorMain should be corrected indeed, thanks for reminding. However, for argument "topology", in case we have input --config to indicate a config file, that file should contain the required topologyName. This means, argument "topology" is just optional for overriding the topologyName configured in config file. 2. I cannot see the second and third screenshot you pasted, therefore not quite sure what you were point to exactly. I'll modify the documentation and correct the package name. Thanks. Michael On Tue, Jul 26, 2016 at 8:09 AM, Liangfei.Suwrote: > Thanks, Caoyu. > > #1 is a bug. That should be fixed. Have EAGLE-395 to track that. > BTW: eagle docs are at > https://github.com/eaglemonitoring/eaglemonitoring.github.io. You're > welcome to send PR help us fix this. > > #2. I can see your screenshot. Can you tell us which version are you using? > And probably use attachment for the screenshot would be better? > > Ralph > > > On Mon, Jul 25, 2016 at 11:44 AM, caoyu03 wrote: > > > HI eagle dev: > > > > I wish use eagle to our product cluster .now,im study it in CDH test > > cluster. > > > > But the doc guide for sandbox. I wish the doc wirte for CDH or apache > > hadoop. > > > > > > and the doc is not good . it too simple. please prefect logical > structure. > > > > > > > > some bug: > > > > > > 1. Step 4: Submit topologies > > > > # start HDFS audilt log monitoring > > > > $ bin/eagle-topology.sh --main > > eagle.security.auditlog.HdfsAuditLogProcessorMain --config > > conf/-hdfsAuditLog-application.conf start > > > > > > --main eagle.security.auditlog.HdfsAuditLogProcessorMain need change to > --main > > *org.apache.*eagle.security.auditlog.HdfsAuditLogProcessorMain > *—-topology > > {xxx-topology-name}* > > > > > > > > 2. > > > > > > in my deploy eagle is can see the setup button.my eagle is look like > this: > > > > it’s version differ ? > > > > > > tks. > > > > english is not good . > > > > > > > > > > > > >
Re: need to be assignee
Hi, Ming, Assigned you required permission, please have a try. - Hao On Tue, Jul 26, 2016 at 2:34 PM, Ming Zengwrote: > Hi Eagle Team, > > I want to be an assignee. > > Thank, > Ming >
need to be assignee
Hi Eagle Team, I want to be an assignee. Thank, Ming
[GitHub] incubator-eagle pull request #276: Updated code to support Druid Sum/Count Q...
GitHub user senthilec566 opened a pull request: https://github.com/apache/incubator-eagle/pull/276 Updated code to support Druid Sum/Count Query Code has been updated to Support Druid Count/Sum Query in 0.3.1. You can merge this pull request into a Git repository by running: $ git pull https://github.com/senthilec566/incubator-eagle EAGLE-396 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/276.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #276 commit e084586a1117bf5bab7596e7a77eaeb239baf1e7 Author: senthilkumarDate: 2016-07-26T06:33:18Z Updated code to support Druid Sum/Count Query --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (EAGLE-396) Support for Sum/Count in Druid Query - System Metrics
Senthilkumar created EAGLE-396: -- Summary: Support for Sum/Count in Druid Query - System Metrics Key: EAGLE-396 URL: https://issues.apache.org/jira/browse/EAGLE-396 Project: Eagle Issue Type: New Feature Affects Versions: v0.3.1 Reporter: Senthilkumar Assignee: Senthilkumar Fix For: v0.3.1 Support for Sum/Count in Druid Query - System Metrics -- This message was sent by Atlassian JIRA (v6.3.4#6332)