Identifying a monitoring template for a managed service based on a service-level agreement

• US 10,122,594 B2
• Filed: 12/05/2013
• Issued: 11/06/2018
• Est. Priority Date: 12/05/2013
• Status: Active Grant

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Jayaprakash, Arun
• Primary Examiner(s): Nguyen, Thu Ha T
• Application Number:
  US15/032,643
• Publication Number:
  US 20160248638A1
• Time in Patent Office: 1,797 Days
• Field of Search: 709223, 709224
• 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 first-level tag on a service template used for implementing the managed service, wherein the first-level tag on the service template and a second-level tag on a service element are based on the SLA, the managed service being a cloud-computing service deployed on a cloud-computing infrastructure including computing hardware, wherein the service element is a computing resource used to implement the managed service in a cloud such as a server, a network, a physical memory, a storage, or an application;

in response to a match between the tag on the monitoring template and the first-level tag on the service template, identifying the monitoring template for the managed service;

monitoring the managed service according to the identified monitoring template; and

applying the monitoring template to the service template.

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

3. The method of claim 1, further comprising:

comparing the tag on the monitoring template with the second-level tag associated with the 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 second-level tag associated with the service element on the service template, identifying the monitoring template for the managed service.

4. The method of claim 1, wherein identifying the monitoring template for the managed service comprises:

determining a plurality of available monitoring templates that correspond to the first-level tag of the service template; and

selecting one of the available monitoring templates as the identified monitoring template.

5. The method of claim 4, wherein identifying the monitoring template for the managed service further comprises:

filtering the available monitoring templates based on the second-level tag of the service element of the service template,

wherein the one of the available monitored templates is selected from the filtered available monitoring templates.

6. The method of claim 5, wherein the service template has a plurality of service elements.

7. The method of claim 6, wherein the service elements each correspond to a computing resource that the managed service uses.

8. The method of claim 5, wherein the second level-tag of the service element indicates a monitoring service complexity required by the service element.

9. The method of claim 1, wherein the tag of the service template indicates a monitoring service complexity required by the service template.

10. 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, the managed service being a cloud-computing service deployed on a cloud-computing infrastructure including computing hardware and a second-level tag for a service element, wherein the service element is a computing resource used to implement the managed service in a cloud such as a server, a network, a physical memory, a storage, and an application;

querying, 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 applying the identified single monitoring template to the service template for monitoring the managed service; and

monitoring the managed service according to the identified monitoring template.

11. The method of claim 10, further comprising:

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

in response to identifying a plurality of monitoring templates with the tag 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.

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

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

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

15. A system, comprising:

a processor;

a non-transitory computer-readable data storage medium storing code executable by the processor to;

define a first-level tag for a service template used for implementing a managed cloud service deployed on a cloud-computing infrastructure including computing hardware;

define a second-level tag for a service element, wherein the service element is a computing resource used to implement the managed cloud service in a cloud such as a server, a network, a physical memory, a storage, and an application; and

receive a query, based on the first-level tag, for identifying monitoring templates with a tag corresponding to the first-level tag, the managed cloud service monitored according to a monitoring template selected from the identified monitoring templates.

16. The system of claim 15, wherein the code is executable by the processor to further:

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

filter the identified monitoring templates based on the second-level tag for the service element present in the service template.

17. The system of claim 16, wherein the code is executable by the processor to further display results of the filtration.

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

19. 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, the managed service being a cloud-computing service deployed on a cloud-computing infrastructure including computing hardware;

define a second-level tag for a service element in the service template, wherein the service element is a computing resource used to implement the managed service in a cloud such as a server, a network, a physical memory, a storage, and an application;

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;

display filtered monitoring templates, the managed service monitored according to a monitoring template selected from the filtered monitoring templates.