Skip to Content

This post describes monitoring results in the Alert Inbox application and helps to understand different rating situations. There are four key figures within the Due List Log monitoring object:

  1. No documents created.
  2. Too few documents created.
  3. Number of messages.
  4. Critical messages.

 

  1. Key Figure: No documents created.

You can pick one of following Due List types: “Picking”, “Delivery” or “Billing”.

You can choose aggregation “per Log” or “per Hour” and rating for the alert – yellow or red.

In the following example, due list for “Delivery” with aggregation “per Log” is being monitored. If the condition is met, a red alert should appear:

Case 1: Grey Alert appeared

In our example, the alert appeared on 09.05.2018 at 14:41 and since then there was no new due list log in the managed system. This means that since then the data collection did not return any result. After the expiry of the specified retention time, the “current” status became grey.

Alert is still visible in the alert inbox as there was a red or yellow alert in the past that has not yet been solved (“worst” column).

Hint: Below screen shot illustrates where to set the retention time in the monitoring object configuration:

Case 2: Red or Yellow Alert appeared:

Rating is red because there is a new occurence that met the alerting criteria – no documents were created on the managed system as per due list run.

The below screen shot illustrates the output of the monitoring on the managed system that can be seen after accessing from Alert Details link “Launch Detail Analysis on System X”

The alert will remain in red status as long as new occurrences (no documents created) will be appearing or until the retention time has been reached. After that, it will turn into grey rating.

Case 3: No alert appeared

Alert will not appear in two situations:

  • the monitoring object has been activated before the due list run (both “current” and “worst” statuses are grey). Only after the trigger of a due list run on managed system, the rating would change
  • referring to this example, in the case that at least 1 document was created per due list run and the previous alert is out of retention time, an alert will not appear in the alert inbox. This is a correct behaviour.

 

2. Key Figure: Too few documents created.

In the following example, due list for “Billing” with aggregation “per Log” is being monitored. If the selected criterion is met, depending on a configured threshold, a yellow or red alert should appear:

Case 1: Grey Alert appeared

In our example, the alert appeared on 11.05.2018 at 16:14 and since then there were no new due list log in the managed system. This means that since then the data collection did not return any result. After the expiry of the specified retention time, the “current” status became grey.

Alert is still visible in the alert inbox as there was a red or yellow alert in the past that has not yet been solved (“worst” column).

Case 2: Red or Yellow Alert appeared

Rating is red because there is a new occurrence that met the alerting criteria – only one or less billing documents were created as per due list run.

The below screen shot illustrates the output of the monitoring on the managed system that can be seen after accessing from Alert Details link “Launch Detail Analysis on System X”

The alert will remain in red status as long as new occurrences will be appearing or until the retention time has been reached. After that, it will turn into grey rating.

Case 3: No alert appeared

Referring to this example, an alert will not appear in the alert inbox in the case that at least 3 documents were created per due list run and the alert is out of retention time. This is a correct behaviour.

 

3. Key Figure: Number of messages.

In the following example, due list for “Billing” with aggregation “per Log” is being monitored. If the selected criterion is met, depending on a configured threshold, a yellow or red alert should appear:

Case 1: Grey Alert appeared

In our example, the alert appeared on 11.05.2018 at 16:19 and since then there was no new due list log in the managed system. This means that since then the data collection did not return any result. After the expiry of the specified retention time, the “current” status became grey.

Alert is still visible in the alert inbox as there was a red or yellow alert in the past that has not yet been solved (“worst” column).

Case 2: Red or Yellow Alert appeared

Rating is red because there is a new occurrence that met the alerting criteria – more than two messages were raised on the managed system as per due list run.

The below screen shot illustrates the output of the monitoring on the managed system that can be seen after accessing from Alert Details link “Launch Detail Analysis on System X”

The alert will remain in red status as long as new occurrences will be appearing or until the retention time has been reached. After that, it will turn into grey rating.

Case 3: No alert appeared

Alert will not appear in two situations:

  • the monitoring object has been activated before the due list run (both “current” and “worst” statuses are grey). Only after the trigger of a due list run on managed system, the rating would change
  • referring to this example, in the case that no messages were raised per due list run and the alert is out of retention time, an alert will not appear in the alert inbox. This is a correct behaviour.

 

4. Key Figure: Critical messages

In the following example, due list for “Billing” with aggregation “per Log” is being monitored. If the selected criterion is met, depending on a configured threshold, a yellow or red alert should appear:

Case 1: Grey Alert appeared

In our example, the alert appeared on 11.05.2018 at 16:19 and since then there was no new due list log in the managed system. This means that since then the data collection did not return any result. After the expiry of the specified retention time, the “current” status became grey.

Alert is still visible in the alert inbox as there was a red or yellow alert in the past that has not yet been solved (“worst” column).

Case 2: Red or Yellow Alert appeared

Rating is yellow because there is a new occurrence that met the alerting criteria – more than one and less than 10 error messages were raised on the managed system as per due list run.

The below screen shot illustrates the output of the monitoring on the managed system that can be seen after accessing from Alert Details link “Launch Detail Analysis on System X”

Case 3: No alert appeared

Referring to this example, an alert will not appear in the alert inbox in the case that no critical messages appeared on the managed system per due list run and the alert is out of retention time. This is a correct behaviour.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply