Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

Help with Monitoring Time Range option


From the Doc:

Select a non-default Monitoring
Time Range

The list is active only for Enterprise
Synthetic and sequence
type of alerts and only if the Transaction source
dimension is filtered to Transactions
(Active Monitoring)
. Use this option if you wish to evaluate
alert condition on the Enterprise Synthetic data covering interval different
than the default Last
monitoring interval
(5 minutes by default) used by the CAS. As
the Enterprise Synthetic transactions spanning across two consecutive intervals
will not raise an alert, even if they meet the defined alert conditions, you
can select a CAS independent time range to avoid such situations. You can
choose among the following predefined ranges: 10, 15, 30 and 60 minutes.

Question. Does this option cover the alert if we are running ESM
transactions every 15 minutes? So for example, we need to set this option to 15
because if it is set to the last interval or 10, the CAS would miss the alert? If
yes, what if it were set to 20 or 30 and ESM scripts run every 15 min? Also,
does this impact or take precedent over the “Raise after “x” interval(s) under
Propagation settings in any way or completely different? Thanks in advance for
the help.



Hi @Matthew k,

We are also struggling with the same scenerio to generate alerts in the range for predefined like: 20 or 30 mins. Our requirement is to generate alerts for 3 consecutive failures of any ESM script.

Kindly let us know if you have find any solution to this requirement.

Many Thanks,

Vinay Chaudhary

DynaMight Advisor
DynaMight Advisor


I haven't been able to find any documentation regarding this "Monitoring time range" option - does anything exist?

Hello anonymous user

If you are asking about the CAS then please follow the link for the configuring section-specific time ranges.

Below link is about the Enterprise Synthetic.




We're talking about defining alerts at the RUM console based on Enterprise Synthetic data. I'm afraid the links you provided aren't related to this issue...

Hello anonymous user

Oops ! We have only the propagation settings to handle the triggering condition.



Not only the propagation settings; ESM data has an additional setting under "Detection settings" -> "Monitored metric" -> "Monitoring time range". That is what we're trying to get further info on.