At my client, we have a few incidents that are triggered by slow running mainframe programs. Sometimes the mainframe program times out on the mainframe side after 60 seconds, but dynatrace doesn't recognize that for some reason, and the purepath will run for ten minutes and timeout (default timeout).
Is there any way that exists to exclude timed out purepaths from measures/incidents so that they do not affect our averages or throw false-positive alerts?
P.S. We don't care about the purepath being timed out. As far as we are concerned, timed out purepaths are dead to us. Is excluding timed out purepaths from measures a possibility. Yes/No? Is it something to come in future versions?
Same day last week 1 Answer
Are web request filters unreliable? 3 Answers