[
https://issues.apache.org/jira/browse/METRON-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15819897#comment-15819897
]
ASF GitHub Bot commented on METRON-532:
---------------------------------------
Github user mattf-horton commented on the issue:
https://github.com/apache/incubator-metron/pull/414
@cestella @mmiklavc @nickwallen , thank you for the review comments.
Please see latest for improvements to comments per your suggestions. No code
was changed. Also fixed a doc bug regarding profiler "init" syntax in example
code.
This code has been validated on a single-node 16GB Centos7 vm with
OracleJDK8, HDP-2.5.3, and Ambari-2.4.2. The cluster was installed via my
metron-mpack-singlenode, then Profiler was added with @nickwallen 's RPMs. Bro
data was pumped through the usual sequence of topologies, and was observed in
Storm UI to propagate through all into indexer and profiler. Elasticsearch and
HBase were queried from outside Metron to confirm presence and format of data,
and PROFILE_GET was used in Stellar REPL to read the profile data back out as
expected. Use of the config_overrides map argument in PROFILE_GET was also
observed to be effective.
> Define Profile Period When Calling PROFILE_GET
> ----------------------------------------------
>
> Key: METRON-532
> URL: https://issues.apache.org/jira/browse/METRON-532
> Project: Metron
> Issue Type: Improvement
> Reporter: Nick Allen
> Assignee: Matt Foley
> Fix For: 0.3.0
>
>
> The Profiler Client currently offers the PROFILE_GET Stellar function to
> access profile data. The work done for METRON-529 allowed the user to
> customize the profile period using Metron global properties.
> A user may need to access historical profiles with different durations and
> would want to specify the period as part of the call to the Profiler Client,
> rather than in the Metron global properties.
> This would be especially necessary should METRON-530 be completed allowing
> different profiles to use different period durations simultaneously.
> There is some discussion of this attached to METRON-529.
> See also discussion in METRON-594 "Replay Telemetry Data through Profiler".
> Note: At suggestion of [~cestella], scope of this work item was expanded to
> include checking for config changes at run time, in the PROFILE_GET Stellar
> function.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
