Geoff B. avatar image
Geoff B. asked ·

Problem re-opening timeframe

Hi Community,

I have synthetic tests that create problems as soon as 2/3 locations fail. These problems immediately send emails to support teams as an FYI.

We have a secondary Alerting profile that will send the problem to our NOC team if the problem stays open for 15 minutes.

The problem we have with this system is that if the tests are being a bit intermittent, the problem will resolve itself and then re-open again. This doesn't reset the clock on the problem timer, so an alert goes to the NOC which is going to start MI processes.

We don't want alerts going to the NOC if the test failure is intermittent, only if it's hard down.

(Yes I know we could set up 2/3 locations failing 3 times consecutively, but that prevents us from sending the email alerts to the support team for intermittent failures (fail, fail, pass, fail, pass, pass, fail, pass etc)

My question is, do you know how long a problem has to be closed for before a new one is raised rather than re-opening the 1st one?

dynatrace saasproblem detection
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

1 Answer

Chad T. avatar image
Chad T. answered ·

I believe that full closure takes 3-5 mins, but dont quote me on that lol

10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Space Topics

mobile monitoring dotnet synthetic monitoring reports iis chat kubernetes servicenow amazon web services mysql mainframe rest api errors cassandra dashboard oneagent sdk cmc application monitoring openkit smartscape request attributes monitoring developer community user tagging log monitoring services ufo syntheticadvisory activegate ip addresses auto-detection high five award oracle hyperion webserver uem usql iib test automation license web performance monitoring ios news migration management zones index ibm mq web services custom event alerts notifications sso host monitoring knowledge sharing reports browser monitors java hybris sap vmware maintenance window user action naming javascript appmon ai synthetic classic availability tipstricks automation extensions session replay diagnostic tools permissions davis assistant faq documentation problem detection http monitors server easytravel apdex aws-quickstart network docker tags and metadata cloud foundry google cloud platform synthetic monitoring process groups account usability dynatrace saas gui paas openshift key user actions administration user actions postgresql synthetic locations oneagent security Dynatrace Managed user management custom python technologies mongodb openstack user session monitoring continuous delivery citrix configuration alerting NGINX action naming linux nam installation masking error reporting database mission control jmeter recorder apache mobileapp RUM php threshold azure purepath davis scripting agent aix nodejs android