[
https://issues.apache.org/jira/browse/METRON-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757207#comment-15757207
]
ASF GitHub Bot commented on METRON-590:
---------------------------------------
Github user nickwallen commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/395#discussion_r92923500
--- Diff:
metron-platform/metron-common/src/test/java/org/apache/metron/common/utils/StellarExecutor.java
---
@@ -0,0 +1,84 @@
+package org.apache.metron.common.utils;
--- End diff --
Ah, yes, good catch. We should bring these two together. Hmm.
The immediate problem for me with `StellarProcessorUtils` as-is, is that I
can't set a function resolver. If I simply add another 'run' method so the user
can specify a function resolver, then we're going to have quite a few different
run methods, which gets a little confusing in my opinion.
The other thing I prefer about the approach of `StellarExecutor` is that
each time I call `run` I don't need to pass in all of the extraneous data
structures, like the function resolver, the context and the variable resolver.
I'd prefer to have a way to set all of these, in the `setup` method of my test.
I think this makes each individual test case easier to read.
Which do you prefer? If we can find one way of doing it, I'd be willing to
go through and transition everything to one way or the other.
> Enable Use of Event Time in Profiler
> ------------------------------------
>
> Key: METRON-590
> URL: https://issues.apache.org/jira/browse/METRON-590
> Project: Metron
> Issue Type: Improvement
> Reporter: Nick Allen
> Assignee: Nick Allen
>
> There are at least two different times that are important to consider when
> handling the telemetry messages received by Metron.
> (1) Processing time is the time at which Metron processed the message.
> (2) Event time is the time at which the event actually occurred.
> If Metron is consuming live data and all is well, the processing and event
> times may remain close and consistent. When processing time differs from
> event time the data produced by the Profiler may be inaccurate. There are a
> few scenarios under which these times might differ greatly which would
> negatively impact the feature set produced by the Profiler.
> (1) When the system has experienced an outage, for example, a scheduled
> maintenance window. When restarted a high volume of messages will need to be
> processed by the Profiler. The output of the Profiler will indicate an
> increase in activity, although no change in activity actually occurred on the
> target network. This could happen whether the outage was Metron itself or an
> upstream system that feeds data to Metron.
> (2) If the user attempts to replay historical telemetry through the Profiler,
> the Profiler will attribute the activity to the time period in which it was
> processed. Obviously the activity should be attributed to the time period in
> which the raw telemetry events originated in.
> There are some scenarios when processing time might be preferred and other
> use cases where event time is preferred. The Profiler should be enhanced to
> allow it to produce profiles based on either processing time or event time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
