[
https://issues.apache.org/jira/browse/METRON-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880668#comment-15880668
]
ASF GitHub Bot commented on METRON-701:
---------------------------------------
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/449
> Ninja Edit: I think the kafka topic written to should be pulled from
zookeeper...
@cestella I remember now why I settled on making the topic name a static
configuration from the topology properties. Our `BulkMessageWriterBolt` &
`KafkaMessageWriter` classes seem to have been designed to only work with
statically defined topic names. I would have to change those core classes, if
I want to set the topic name dynamically from Zookeeper. And I tend to get
smacked around when coming close to core classes :)
Am I missing something? Is there a way to define the topic dynamically
while using the `BulkMessageWriterBolt` & `KafkaMessageWriter` classes
unchanged?
If not, I'd prefer to keep the topic name as a static property defined in
the topology properties, at least for this PR. My second choice would be to
open a completely separate PR to update those core classes to accept dynamic
topic names. It does not seem like a complex change, but those are core
classes and will likely cause some debate.
> Triage Metrics Produced by the Profiler
> ---------------------------------------
>
> Key: METRON-701
> URL: https://issues.apache.org/jira/browse/METRON-701
> Project: Metron
> Issue Type: Improvement
> Reporter: Nick Allen
> Assignee: Nick Allen
>
> h3. Problem
> The motivating example is that I would like to create an alert if the number
> of inbound flows to any host over a 15 minute interval is abnormal.
> The value being interrogated here, the number of inbound flows, is not a
> static value contained within any single telemetry message. This value is
> calculated across multiple messages by the Profiler. The current Threat
> Triage process cannot be used to interrogate values calculated by the
> Profiler.
> h3. Proposed Solution
> I am proposing that we treat the Profiler as a source of telemetry. The
> measurements captured by the Profiler would be enqueued into a Kafka topic.
> We would then treat those Profiler messages like any other telemetry. We
> would parse, enrich, triage, and index those messages.
> This would have the following advantages.
> 1. We would be able to reuse the same threat triage mechanism for values
> calculated by the Profiler.
> 2. We would be able to generate profiles from the profiled data - aka
> meta-profiles anyone?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
