Time Span Filtering

Time Span Filtering

Technical Complexity

Medium

Filtering Class

Information Aggregation

Purpose

  • Avoid false detection of transient faults. These faults can be logged and monitored by another instance, but this end point will only receive stable faults. 
  • Wait a certain period of time, and forward only the dominant event within that period to the event listener.

Situation

  • A network connection is deemed unpredictable. It has fluke (transients) failures occurring all the time. But only when the network will be down more than 20% of the time, that the fault will be send to the event listener.

Design

IEP deals with streams, but allow us to work with relations with this the process. In this case, we want to do the following:

  1. Set a time window that is large enough to avoid boundary conditions, but small enough to make quick decisions
  2. Count the number of events that will allow us to make a decision on the outcome (ON/OFF events)
  3. Make the decision which is the most relevant event.
  4. Each time a decision is made (every 10 seconds), and that a higher than 20% down rate is detected, insert a new event it the outbound stream.

IEP Constructs Used

Process Flow


  • Inbound stream, System State Event Stream
  • Time Based Aggregation Window Converter
  • On and Off counts
  • Relation joint, decision point
  • Convert to insert event for the output stream
  • Output stream, Fluke count stream

Time Based Aggregation


 
In this sample, we will do an event aggregation every 10 seconds, which will take into account all events that occured in the last 30 seconds. This provides us with a "moving average" model we can use here.

Relevant Event Type Counts

On Counts

Off Counts

  Here, we count the number of event we want from the time based aggregation. This allow us to create a stream of a single event type, so we can process it to generate a single summary event that is relevant to us.

Decision point, the ON/OFF count comparison



At the decision point, we are left with the simple need to compare which count we have the most and to forward this event. Only when the OFF rate is greater than a 5th of the ON rate, an event will be forwarded to the outstream.

Sample Files

Example Limitations

Labels

component-iepse component-iepse Delete
component-serviceengine component-serviceengine Delete
type-howto type-howto Delete
type-workshop type-workshop Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact