Systems and methods for application operational monitoring
A method for application operational monitoring may include an operational monitoring computer program: (1) ingesting a plurality of service level indicator (SLI) metrics for an application, each SLI metric identifying a number of successful observations and a number of total observations; (2) calculating a SLI score for each SLI metric based on the number of successful observations and the number of total observations for the SLI metric; (3) weighting the SLI score for each SLI metric; (4) combining the weighted SLI scores into an application SLI score; (5) calculating a calculated error budget based on the application SLI score; (6) determining that the calculated error budget exceeds an error budget for the application; (7) generating a notification in response to the calculated error budget breaching the error budget; and (8) causing implementation of a restriction on the application, wherein the restriction prevents enhancements to the application.
1. A method for application operational monitoring, comprising:
ingesting, at an operational monitoring computer program, a plurality of service level indicator (SLI) metrics for an application comprising synthetic SLI metrics and Application Performance Monitoring (APM)/Application Programmable Interface (API) SLI metrics, each SLI metric identifying a number of successful observations and a number of total observations;
calculating, by the operational monitoring computer program, a SLI score for each SLI metric based on the number of successful observations and the number of total observations for the SLI metric;
weighting, by the operational monitoring computer program, the SLI score for each SLI metric;
combining, by the operational monitoring computer program, the weighted SLI scores into an application SLI score;
calculating, by the operational monitoring computer program, a calculated error budget based on the application SLI score;
comparing, by the operational monitoring computer program, the calculated error budget to an error budget for the application;
generating, by the operational monitoring computer program, a notification in response to the comparison;
in response to the calculated error budget breaching the error budget, causing, by the operational monitoring computer program, implementation of a restriction in an integrated deployment toolchain/pipeline for the application, wherein the restriction prevents enhancements to the application and prevents the application from executing further operations; and
in response to the calculated error budget being within the error budget, causing, by the operational monitoring computer program, the restriction to be removed.
2. The method of claim 1 , further comprising:
calculating, the operational monitoring computer program, the error budget based on a service level objective (SLO) for the application.
3. The method of claim 2 , wherein the error budget is based on the number of total observations.
4. The method of claim 1 , wherein the notification comprises a SLO status.
5. The method of claim 1 , further comprising:
updating, by the operational monitoring computer program, the error budget based at least one prior calculated error budget for the application.
6. An electronic device, comprising:
a computer processor; and
a memory comprising an operational monitoring computer program;
wherein the operational monitoring computer program is configured to:
ingest a plurality of service level indicator (SLI) metrics for an application comprising synthetic SLI metrics and Application Performance Monitoring (APM)/Application Programmable Interface (API) SLI metrics, each SLI metric identifying a number of successful observations and a number of total observations;
calculate a SLI score for each SLI metric based on the number of successful observations and the number of total observations for the SLI metric;
weight the SLI score for each SLI metric;
combine the weighted SLI scores into an application SLI score;
calculate a calculated error budget based on the application SLI score;
compare the calculated error budget to an error budget for the application;
generate a notification in response to the comparison;
in response to the calculated error budget breaching the error budget, cause implementation of a restriction in an integrated deployment toolchain/pipeline for the application, wherein the restriction prevents enhancements to the application and prevents the application from executing further operations; and
in response to the calculated error budget being within the error budget, cause the restriction to be removed.
7. The electronic device of claim 6 , wherein the operational monitoring computer program is further configured to:
calculate the error budget based on a service level objective (SLO) for the application.
8. The electronic device of claim 7 , wherein the error budget is based on the number of total observations.
9. The electronic device of claim 6 , wherein the notification comprises a SLO status.
10. The electronic device of claim 6 , wherein the operational monitoring computer program is further configured to:
update the error budget based on at least one prior calculated error budget for the application.
11. A system, comprising:
an application;
a monitoring broker application that receives plurality of service level indicator (SLI) metrics comprising synthetic SLI metrics and Application Performance Monitoring (APM)/Application Programmable Interface (API) SLI metrics from the application and makes them available on a telemetry bus, each SLI metric identifying a number of successful observations and a number of total observations; and
an operational monitoring engine comprising a computer processor and executing an operational monitoring computer program that receives the plurality of SLI metrics from the telemetry bus and is configured to:
ingest the SLI metrics;
calculate a SLI score for each SLI metric based on the number of successful observations and the number of total observations for the SLI metric;
weight the SLI score for each SLI metric;
combine the weighted SLI scores into an application SLI score;
calculate a calculated error budget based on the application SLI score;
compare the calculated error budget to an error budget for the application;
generate a notification in response to the comparison;
in response to the calculated error budget breaching the error budget, cause implementation of a restriction in an integrated deployment toolchain/pipeline for the application, wherein the restriction prevents enhancements to the application and prevents the application from executing further operations; and
in response to the calculated error budget being within the error budget, cause the restriction to be removed.
12. The system of claim 11 , wherein the operational monitoring computer program is further configured to calculate the error budget based on a service level objective (SLO) for the application, wherein the error budget is based on the number of total observations.
13. The system of claim 11 , wherein the notification comprises a SLO status.
14. The system of claim 11 , wherein the operational monitoring computer program is further configured to update the error budget based on at least one prior calculated error budget for the application.