You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Nick Allen (JIRA)" <ji...@apache.org> on 2016/11/28 15:52:58 UTC
[jira] [Updated] (METRON-590) Enable Use of Event Time in Profiler
[ https://issues.apache.org/jira/browse/METRON-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Allen updated METRON-590:
------------------------------
Description:
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, these times may remain close and consistent. There are many scenarios under which these times might differ greatly. For example, if there are delays in processing messages due to heavy load or if older, archived telemetry is being replayed through the system.
When processing time differs from event time the data produced by the Profiler may be inaccurate. There are some use cases 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.
was:
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, these times may remain close and consistent. There are many scenarios under which these times might differ greatly. For example, if there are delays in processing messages due to heavy load or if older, archived telemetry is being replayed through the system.
When processing time differs from event time the data produced by the Profiler may be inaccurate. The Profiler should be enhanced to allow it to produce profiles based on either processing time or event time.
> 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, these times may remain close and consistent. There are many scenarios under which these times might differ greatly. For example, if there are delays in processing messages due to heavy load or if older, archived telemetry is being replayed through the system.
> When processing time differs from event time the data produced by the Profiler may be inaccurate. There are some use cases 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)