Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section
bordertrue
Panel
titleEnvironment
borderStylesolid
  • Dynatrace Portal
  • Alerts
Panel
titleSolution
borderStylesolid

You can configure an alert so the alert is triggered only after the specified number of consecutive errors. Using this feature can prevent "false alarms": a single error or failure may be the result of a random occurrence and isn't always an indication of a performance issue.

You can set the number of consecutive errors, from 1 through 5, for all alert types.

The examples below, for Transaction Failure Alerts, describe how does the consecutive error setting works.

Example 1:

Transaction Failure Alert Configuration for test named Example:

  • Three nodes are configured: Node A, Node B, and Node C.
  • The Number of consecutive errors is set to 3.
  • The Node Thresholds is 1 node.

When any node consecutively reports 3 failures, the alert is triggered.

If Node A reports 1 failure and the next run on Node A is successful, while the other two nodes run successfully in all test runs, no alert is triggered.

Example 2:

Transaction Failure Alert Configuration for test named Example:

  • Three nodes are configured: Node A, Node B, and Node C.
  • The Number of consecutive errors is set to 3.
  • The Node Thresholds is 2 nodes.
With this configuration, an alert is triggered when 2 nodes each have three consecutive errors.

In the first test interval, Nodes A, B and C all fail. All nodes have an error count of 1.

In the second test interval, Node A runs successfully, Node B fails, and Node C fails. The error count for Node A is updated to 0; Node B to 2, and Node C to 2.

If in the third test interval, Node A fails, Node B fails, and Node C runs successfully, the error count for Node A is updated to 01, Node B to 3, and Node C to 0. The alert is not triggered because only 1 node has 3 consecutive errors.

However, if in the third test interval, Node A fails, Node B fails, and Node C fails, the error count for Node A is updated to 01, Node B to 3, and Node C to 3. The alert is triggered because 2 nodes have 3 consecutive errors.

 Node AError count ANode BError count BNode CError count CTrigger alert?
First runFail1Fail1Fail1NO
Second runGood0Fail2Fail2NO
Third run(Scenario I)Fail1Fail3Good0NO
Third run(Scenario II)Fail21Fail3Fail3YES