SITE RELIABILITY ENGINEERING AS A SERVICE (SREAAS) FOR SOFTWARE PRODUCTS
Site reliability engineering (SRE) may be provided as a service to software products, such as an on-premises software product residing at a first computing environment. A SRE service site may be hosted at a second computing environment that is remote and separate from the first computing environment. A SRE agent resides at the first computing environment to monitor the software product, and provides information, such as metric data or log information pertaining to the software product, to the SRE service site. A SRE service of the SRE service site performs analysis of the information to identify an issue with the software product, diagnosis to determine a cause of the issue, and identifies a remediation that may be applied by the SRE agent to address the issue.
1 . A method to provide site reliability engineering (SRE) as a service for software products residing in a first computing environment, the method comprising:
implementing a SRE service site, which provides the SRE service, at a second computing environment remote from the first computing environment;
implementing a SRE agent at the first computing environment, wherein the SRE agent is configured to obtain information regarding a software product in the first computing environment and to provide the obtained information to the SRE service site;
analyzing, at the SRE service site, the information provided by the SRE agent to identify an issue pertaining to the software product;
performing diagnosis, at the SRE service site, to identify a cause of the issue;
determining, at the SRE service site and from the cause of the issue, a remediation to address the issue; and
instructing the SRE agent to apply the remediation at the first computing environment.
2 . The method of claim 1 , wherein the first computing environment includes a virtualized computing environment where the software product resides.
3 . The method of claim 1 , wherein performing the diagnosis and determining the remediation respectively comprise:
using a diagnostic script stored at a diagnosis repository at the SRE service site to identify the cause of the issue; and
using a remediation script stored at a remediation repository at the SRE service site to determine the remediation to address the issue.
4 . The method of claim 1 , further comprising updating the SRE agent in response to a change in the software product.
5 . The method of claim 1 , further comprising after having analyzed the information and identified the issue:
triggering the performing the diagnosis to identify the cause of the issue;
generating an alarm to notify a first entity, being a user of the software product, of the issue; and
generating a ticket to inform a second entity, being a provider of the software product, of the issue,
wherein reference information exists at the SRE service site that is applicable to the issue.
6 . The method of claim 1 , further comprising after having analyzed the information and identified the issue:
generating an alarm to notify a first entity, being a user of the software product, of the issue; and
generating a ticket to inform a second entity, being a provider of the software product, of the issue,
wherein the issue is a new issue at the first computing environment for which reference information applicable to the issue is absent from the SRE service site.
7 . The method of claim 1 , wherein:
a first entity is a user of the software product,
a second entity is a provider of the software product,
a third entity maintains the SRE service site and the SRE agent, and
the third entity provides at least one interface to the SRE service and to the SRE agent to enable the second entity to update functionality of the SRE service and the SRE agent.
8 . The method of claim 7 , further comprising maintaining, at the SRE service site, at least one or more of:
a first repository to store reference metric information;
a second repository to store reference diagnosis information;
a third repository to store reference remediation information,
wherein the second entity provides and updates the reference metric information, the reference diagnosis information, and the reference remediation information.
9 . A non-transitory computer-readable medium having instructions stored thereon, which in response to execution by one or more processors, cause the one or more processors to perform or control performance of a method to provide site reliability engineering (SRE) as a service for a software product residing in a first computing environment, wherein the method comprises:
receiving, at a SRE service site hosted at a second computing environment remote from the first computing environment, information from a SRE agent residing at the first computing environment, wherein the information is collected by the SRE agent and pertains to operational behavior of the software product;
analyzing, at the SRE service site, the information received from the SRE agent to identify an issue pertaining to the software product;
performing diagnosis, at the SRE service site, to identify a cause of the issue;
determining, at the SRE service site and from the cause of the issue, a remediation to address the issue; and
instructing the SRE agent to apply the remediation at the first computing environment.
10 . The non-transitory computer-readable medium of claim 9 , wherein performing the diagnosis and determining the remediation respectively comprise:
using a diagnostic script stored at a diagnosis repository at the SRE service site to identify the cause of the issue; and
using a remediation script stored at a remediation repository at the SRE service site to determine the remediation to address the issue.
11 . The non-transitory computer-readable medium of claim 9 , wherein the method further comprises updating the SRE agent in response to a change in the software product.
12 . The non-transitory computer-readable medium of claim 9 , wherein the method further comprises after having analyzed the information and identified the issue:
triggering the performing the diagnosis to identify the cause of the issue;
generating an alarm to notify a first entity, being a user of the software product, of the issue; and
generating a ticket to inform a second entity, being a provider of the software product, of the issue,
wherein reference information exists at the SRE service site that is applicable to the issue.
13 . The non-transitory computer-readable medium of claim 9 , further comprising after having analyzed the information and identified the issue:
generating an alarm to notify a first entity, being a user of the software product, of the issue; and
generating a ticket to inform a second entity, being a provider of the software product, of the issue,
wherein the issue is a new issue at the first computing environment for which reference information applicable to the issue is absent from the SRE service site.
14 . The non-transitory computer-readable medium of claim 9 , wherein the method further comprises providing an interface to the SRE service site to enable an entity, which provides the software product, to update functionality of the SRE service site or the SRE agent.
15 . A system to provide site reliability engineering (SRE) as a service for a software product residing at a remote computing environment, the system comprising:
one or more processors; and
a non-transitory computer-readable medium coupled to the one or more processors and having instructions stored thereon which, in response to execution by the one or more processors, cause the one or more processors to perform operations to:
receive, from a SRE agent residing at the remote computing environment, information collected by the SRE agent and that pertains to operational behavior of the software product;
operate an analysis unit to identify, from the information received from the SRE agent, an issue pertaining to the software product;
operate a diagnosis unit to identify a cause of the issue; and
operate a remediation unit to determine, from the cause of the issue, a remediation to address the issue, wherein the remediation unit is configured to instruct the SRE agent to apply the remediation at the remote computing environment.
16 . The system of claim 15 , wherein the instructions, in response to execution by the one or more processors, further cause the one or more processors to perform operations to:
provide an interface to enable an entity to update functionality of the SRE agent, wherein the entity is a provider of the software product, and wherein the functionality of the SRE agent is updated in response to a change in the software product.
17 . The system of claim 15 , wherein the instructions, in response to execution by the one or more processors, further cause the one or more processors to perform operations to:
generate an alarm to notify a first entity, being a user of the software product, of the issue; and
generate a ticket to notify a second entity, being a provider of the software product, to investigate the issue to determine the cause of the issue and the remediation to address the issue.
18 . The system of claim 15 , wherein the remote computing environment includes a virtualized computing environment where the SRE agent resides, and wherein the analysis, diagnosis, and remediation units reside in a cloud computing environment.
19 . The system of claim 15 , further comprising:
a first repository to store reference metric information usable by the analysis unit to identify the issue;
a second repository to store reference diagnosis information usable by the diagnosis unit to identify the cause of the issue;
a third repository to store reference remediation information usable by the remediation unit to determine the remediation.
20 . The system of claim 15 , wherein the information received from the SRE agent is received from a proxy.