Response Time Auto-Baselin: violation is shown even when plot values are below auto-baseline

[vishwajit_inamd]

Hi There, we have noticed that appmon shows false violation highlight in red even when the actual RT is below the response time as shown in the snapshot. Also we have seen that there has been below incident exception related oracle PWH.

 Space quota exceeded see attached message for details
        ORA-01654: unable to extend index
        DYNATRACE.INCIDENTPROPERTIES_KEYVAL_IDX by 8192 in tablespace
        SYSTEM - Count: 17

Space quota exceeded see attached message for details
        ORA-01654: unable to extend index
        DYNATRACE.INCIDENTPROPERTIES_PKEY by 8192 in tablespace SYSTEM - Count: 625

Space quota exceeded see attached message for
        details ORA-01654: unable to extend index
        DYNATRACE.INCIDENTPROPERTIES_PKEY by 8192 in tablespace SYSTEM

Is that due to this? Kindly help. (Also is it advisable to resolve table space issue by enabling row movement then compaction, pl. suggest).

[vishwajit_inamd]

Pl. see snapshot here:

[pahofmann · Accepted solution]

The baseline behavior is as expected due to Significant Measures.

A Violation will start when at least two Significant Measures are above the baseline, and it will end once at least one Significant Measure is below the Baseline.

If a Measure is Significant depends e.g. on the current Throughput, you can read more about the base lining here: https://www.dynatrace.com/support/doc/appmon/appli...

You can identify a Significant Measure by hovering over the chart, a Significant Measure will be displayed as a dot:

While this is not related to the PWH incident you are seeing, you should still take care of that.

[waikeat_chan]

Actually, what does 'Significant Measures' really means?

[pahofmann]

It's not 100% percisce in the documentation unfortunately. It means only measures where there is a significant amount of traffic, so that single outliers when there is low traffic do not count.