If the application has any incidents within the current timeframe, the violations history shows a quick overview of current and past problems with your application.
Click it to view the history of all incidents for the current timeframe along with their statuses. Click the incident to switch to the source event for the detailed examination.
Incident statuses explained
In the incident rule you specify the Evaluation Timeframe, which is duration for the incident conditions evaluation. The incident conditions must be fullfilled during this timeframe for an incident to arise. When this happens, the incident is created. It remains open, until the incident measures are below thresholds for the same timeframe.
For example, if you select a timeframe of one minute and use a PurePath duration measure with an average aggregation as input for the incident rule, the average PurePath duration of the last minute is checked for violation every 10 seconds. Measures remain in memory for one hour.
The following graphic illustrates how timeframe is used to check for incidents.
The longer the evaluation timeframe is, the smoother the averaged values will be. Use longer timeframes to reduce the impact of short periods of unusual values that would cause violations with shorter timeframes. The following graphic shows this smoothing effect for different evaluation timeframes. Note how the 10s-values fluctuate wildly while the 60s average provides a much smoother impression. 3m and 10m averages are even smoother and in this example don't show much detail at all.
The evaluation timeframe doesn't have any direct impact on incident duration though. Incidents close only when their condition hasn’t been met for a minute. This more effectively deals with measurements oscillating around their thresholds. Once this timespan has passed without further violation, incidents are closed with the closing time set to fit actual measurements.