Metric for planned downtime

• US 8,212,683 B2
• Filed: 12/09/2009
• Issued: 07/03/2012
• Est. Priority Date: 12/09/2009
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Klein, Udo, Stegmueller, Herbert
• Primary Examiner(s): Nguyen, Tai T
• Application Number:
  US12/634,391
• Publication Number:
  US 20110133945A1
• Time in Patent Office: 937 Days
• Field of Search: 340/652, 340/635, 340/439, 340/540, 340/517, 340/679, 340/636.1, 702/182, 702/187, 702/189
• US Class Current: 340/652
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3055 Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction by redundancy in operation G06F11/14; error detection or correction by redundancy in hardware G06F11/16
• CPC Class Codes: G06F 11/3093 Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes

Abstract

A metric of a system is monitored using a monitoring tool that receives an operation metric and a planned downtime metric that reflects whether the monitored system is currently in a planned downtime, the planned downtime metric received as another one of the multiple metric inputs. The operation metric and the planned downtime metric are combined into a processed operation metric for the monitored system.

Claims

1. A computer-implemented method for monitoring a metric of a system, the method comprising:

receiving, in a monitoring tool and from an agent of the monitoring tool, an operation metric that corresponds to a present characteristic of a monitored system among multiple systems, the monitoring tool receiving the operation metric as one of multiple metric inputs that the monitoring tool is configured to receive from agents;

receiving, in the monitoring tool and from a downtime planning component for the multiple systems, a planned downtime metric that reflects whether the monitored system is currently in a planned downtime, the planned downtime metric received as another one of the multiple metric inputs;

combining the operation metric and the planned downtime metric into a processed operation metric for the monitored system; and

evaluating the processed operation metric with regard to at least one alert rule in the monitoring tool, the alert rule configured to generate an alert to a user of the monitoring tool based on a specific condition relating to the present characteristic.

2. The computer-implemented method of claim 1, wherein

the operation metric satisfies the specific condition;

the planned downtime metric reflects that the monitored system is currently in the planned downtime when the operation metric is received;

the processed operation metric does not satisfy the specific condition due to the operation metric being combined with the planned downtime metric; and

the alert is not generated despite the operation metric satisfying the specific condition.

3. The computer-implemented method of claim 2, further comprising:

generating a report regarding the monitored system using the monitoring tool, the report specifying at least the operation metric and indicating that the operation metric satisfies the specific condition, without the monitoring tool generating the alert.

4. The computer-implemented method of claim 3, wherein the report further indicates using the planned downtime metric that the monitored system is currently in the planned downtime.

5. The computer-implemented method of claim 1, wherein:

the specific condition corresponds to violation of at least one of a maximum allowable value for the present characteristic and a minimum allowable value for the present characteristic;

the operation metric violates at least one of the maximum allowable value and the minimum allowable value when the operation metric is received; and

the processed operation metric is generated so that the processed operation metric complies with the at least one of the maximum allowable value and the minimum allowable value.

6. The computer-implemented method of claim 5, wherein the processed operation metric is defined so that the processed operation metric:

(i) is equal to the operation metric when the planned downtime metric indicates that the monitored system is not currently in the planned downtime; and

(ii) has a predefined value that complies with the at least one of the maximum allowable value and the minimum allowable value when the planned downtime metric indicates that the monitored system is currently in the planned downtime.

7. The computer-implemented method of claim 1, wherein:

the agent is configured to generate the operation metric to have a first value for a predefined acceptable state of the present characteristic;

the downtime planning component is configured to generate the planned downtime metric to have the first value when the monitored system is in the planned downtime; and

the alert rule is configured to generate an alert to a user of the monitoring tool when the processed operation metric does not have the first value.

8. The computer-implemented method of claim 7, wherein the processed operation metric is generated such that the processed operation metric has the first value when at least one of the operation metric and the downtime planning component has the first value.

9. The computer-implemented method of claim 1, wherein:

the specific condition comprises that the current characteristic is higher than an upper limit value;

the downtime planning component is configured to generate the planned downtime metric to (i) have a first value when the monitored system is in the planned downtime, the first value being lower than the upper limit value, and to (ii) have a second value when the monitored system is not in the planned downtime, the second value being higher than the upper limit value; and

wherein the processed operation metric is generated by selecting a lower value of the planned downtime metric and the operation metric.

10. The computer-implemented method of claim 1, wherein:

the specific condition comprises that the current characteristic is lower than a lower limit value;

the downtime planning component is configured to generate the planned downtime metric to (i) have a first value when the monitored system is in the planned downtime, the first value being higher than the lower limit value, and to (ii) have a second value when the monitored system is not in the planned downtime, the second value being lower than the lower limit value; and

wherein the processed operation metric is generated by selecting a higher value of the planned downtime metric and the operation metric.

11. The computer-implemented method of claim 1, further comprising:

determining that the planned downtime metric indicates a first downtime level of multiple downtime levels; and

taking the first downtime level into account when generating the processed operation metric.

12. The computer-implemented method of claim 11, wherein the first downtime level indicates that a database in the monitored system is down.

13. The computer-implemented method of claim 11, wherein the first downtime level indicates downtime in the monitored system with regard to a particular user.

14. The computer-implemented method of claim 1, wherein the downtime planning component is a pseudo-agent of the monitoring tool.

15. A computer program product tangibly embodied in a computer-readable storage medium and comprising instructions that when executed by a processor perform a method for monitoring a metric of a system, the method comprising:

receiving, in a monitoring tool and from an agent of the monitoring tool, an operation metric that corresponds to a present characteristic of a monitored system among multiple systems, the monitoring tool receiving the operation metric as one of multiple metric inputs that the monitoring tool is configured to receive from agents;

receiving, in the monitoring tool and from a downtime planning component for the multiple systems, a planned downtime metric that reflects whether the monitored system is currently in a planned downtime, the planned downtime metric received as another one of the multiple metric inputs;

combining the operation metric and the planned downtime metric into a processed operation metric for the monitored system; and

evaluating the processed operation metric with regard to at least one alert rule in the monitoring tool, the alert rule configured to generate an alert to a user of the monitoring tool based upon a specific condition relating to the present characteristic.

16. A system comprising:

a metric processing component implemented using a computer readable medium, the metric processing component combining (i) an operation metric that corresponds to a present characteristic of a monitored system, and (ii) a planned downtime metric that reflects whether the monitored system is currently in a planned downtime, into a processed operation metric;

a rule processing component implemented using a computer readable medium, the rule processing component configured to evaluate the processed operation metric with regard to at least one alert rule, the alert rule generating an alert based on a specific condition relating to the present characteristic; and

an output device configured to present the alert to a user when generated by the rule processing component.

17. The system of claim 16, further comprising:

a report generating component implemented using a computer readable medium, the report generating component receiving at least the operation metric and being configured to generate a report that specifies at least the operation metric and indicates that the operation metric satisfies the specific condition, without the rule processing component generating the alert.

18. The system of claim 16, implemented in a monitoring tool configured to receive multiple metric inputs from agents, at least one of the agents forwarding the operation metric regarding the monitored system.

19. The system of claim 18, wherein the metric processing component receives the planned downtime metric from a downtime planning component for multiple systems including the monitored system, the downtime planning component being a pseudo-agent of the monitoring tool.

20. The system of claim 16, wherein the metric processing component determines that the planned downtime metric indicates a first downtime level of multiple downtime levels, and takes the first downtime level into account when generating the processed operation metric.