# US 10,122,594 B2 · Identifying a monitoring template for a managed service based on a service-level agreement > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,122,594 B2 - Document ID: US10122594B2 - Status: Granted - Kind: B2 - Application number: 15/032,643 - Filed: 2013-12-05 - Published: 2016-08-25 - Granted: 2018-11-06 - Earliest claimed: 2013-12-05 - Assignees: Hewlett Pacard Enterprise Development LP - Applicants: Hewlett Packard Enterprise Development LP - Inventors: Arun Jayaprakash - Web page: https://patentgrep.com/patent/US10122594B2 ## CPC - G06F 11/3495: {for systems} - G06F 11/006: {Identification (G06F11/2289 takes precedence)} - G06F 16/9535: Search customisation based on user profiles and personalisation - 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] - G06F 11/3409: {for performance assessment} - G06F 2201/875: Monitoring of systems including the internet - H04L 43/20: the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## 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 ### Claim 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. ### Claim 2 (depends on 1) The method of claim 1, wherein the tag indicates a level of complexity of monitoring service defined in the SLA. ### Claim 3 (depends on 1) 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. ### Claim 4 (depends on 1) 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. ### Claim 5 (depends on 4) 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. ### Claim 6 (depends on 5) The method of claim 5, wherein the service template has a plurality of service elements. ### Claim 7 (depends on 6) The method of claim 6, wherein the service elements each correspond to a computing resource that the managed service uses. ### Claim 8 (depends on 5) The method of claim 5, wherein the second level-tag of the service element indicates a monitoring service complexity required by the service element. ### Claim 9 (depends on 1) The method of claim 1, wherein the tag of the service template indicates a monitoring service complexity required by the service template. ### Claim 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. ### Claim 11 (depends on 10) 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. ### Claim 12 (depends on 11) The method of claim 11, further comprising applying the selected monitoring template to the service template for monitoring the managed service. ### Claim 13 (depends on 10) The method of claim 10, wherein the first-level tag and the second-level tag are based on the Service-Level Agreement (SLA). ### Claim 14 (depends on 10) The method of claim 10, wherein the first-level tag and the second-level tag are defined during creation of the service template. ### Claim 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. ### Claim 16 (depends on 15) 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. ### Claim 17 (depends on 16) The system of claim 16, wherein the code is executable by the processor to further display results of the filtration. ### Claim 18 (depends on 15) The system of claim 15, wherein the managed cloud service is hosted on one of a private cloud, public cloud or hybrid cloud. ### Claim 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.