Identifying A Monitoring Template For A Managed Service Based On A Service-Level Agreement

• US 20160248638A1
• Filed: 12/05/2013
• Published: 08/25/2016
• Est. Priority Date: 12/05/2013
• Status: Active Grant

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Jayaprakash, Arun
• Granted Patent: US 10,122,594 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/006 Identification G06F11/2289 takes precedence
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 43/20 the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV

Abstract

Provided is a method of identifying a monitoring template for a managed service based on a Service-Level Agreement (SLA). A tag on a monitoring template is compared with a tag on a service template used for implementing the managed service, wherein the tag on the service template is based on the SLA. In response to a match between the tag on the monitoring template and the tag on the service template, a monitoring template is identified for the managed service.

Claims

1. A method of identifying a monitoring template for a managed service based on a Service-Level Agreement (SLA), comprising:

comparing a tag on the monitoring template with a tag on a service template used for implementing the managed service, wherein the tag on the service template is based on the SLA; and

in response to a match between the tag on the monitoring template and the tag on the service template, identifying the monitoring template for the managed service.

2. The method of claim 1, further comprising applying the monitoring template to the service template.

3. The method of claim 1, wherein the tag indicates a level of complexity of monitoring service defined in the SLA.

4. The method of claim 1, further comprising:

comparing the tag on the monitoring template with a tag associated with a service element on the service template used for implementing the managed service, wherein the tag associated with the service element is based on the SLA; and

in response to a match between the tag on the monitoring template and the tag associated with the service element on the service template, identifying the monitoring template for the managed service.

6. The method of claim 1, further comprising:

defining a second-level tag for a service element in the service template;

in response to identifying a plurality of monitoring templates with the tag to corresponding to the first-level tag, filtering the plurality of monitoring templates based on the second-level tag for the service element; and

allowing selection of a monitoring template from the filtered monitoring templates.

7. The method of claim 6, further comprising applying the selected monitoring template to the service template for monitoring the managed service.

5. A method of identifying a monitoring template for a managed service based on a Service-Level Agreement (SLA), comprising:

defining a first-level tag for a service template used for implementing the managed service;

querying, based on the first-level tag, a monitoring system for identifying a monitoring template with a tag corresponding to the first-level tag; and

in response to identifying only a single monitoring template with the tag corresponding to the first-level tag, automatically applying the identified single monitoring template to the service template for monitoring the managed service.

8. The method of claim 5, wherein the first-level tag and the second-level tag are based on the Service-Level Agreement (SLA).

9. The method of claim 5, wherein the first-level tag and the second-level tag are defined during creation of the service template.

10. A system, comprising:

a service template designer module to define a first-level tag for a service template used for implementing a managed cloud service; and

a monitoring system module to receive a query, based on the first-level tag, for identifying monitoring templates with a tag corresponding to the first-level tag.

11. The system of claim 10, wherein the service template designer module defines a second-level tag for a service element present in the service template;

and

wherein the monitoring system module filters the identified monitoring templates based on the second-level tag for the service element present in the service template.

12. The system of claim 11, further comprising a user interface component to display results of the filtration.

13. The system of claim 10, wherein the managed cloud service is hosted on one of a private cloud, public cloud or hybrid cloud.

14. A non-transitory processor readable medium, the non-transitory processor readable medium comprising machine executable instructions, the machine executable instructions when executed by a processor causes the processor to:

define a first-level tag for a service template used for implementing the managed service;

define a second-level tag for a service element in the service template;

query, based on the first-level tag, a monitoring system for identifying a monitoring template with a tag corresponding to the first-level tag;

in response to identifying only a single monitoring template with the tag corresponding to the first-level tag, automatically apply the identified single monitoring template to the service template for monitoring the managed service;

in response to identifying a plurality of monitoring templates with the tag corresponding to the first-level tag, filter the plurality of monitoring templates based on the second-level tag for the service element; and

display filtered monitoring templates.