Application uptime calculation in hosted environment
In some implementations, there is provided a method that includes monitoring, by an application uptime system, whether execution of an application is successful without causing an incident; in response to the execution of the application being unsuccessful and causing the incident, the method further comprising: collecting one or more end user incident reports including an incident identifier, a start time of the incident, and a stop time of the incident, collecting one or more development system incident reports linked to the one or more end user incident reports, determining at least one end user metric for the application, generating one or more user interface views based on the at least one end user metric for the application, and causing to be presented the one or more user interface views. Related systems, methods, and articles of manufacture are also disclosed.
1. A computer-implemented method, comprising:
monitoring, by an application uptime system, whether execution of an application is successful without causing an incident;
in response to the execution of the application being successful without causing the incident, stopping, by the application uptime system, monitoring of the application until an external trigger is received; and
in response to the execution of the application being unsuccessful and causing the incident, the method further comprising:
collecting, by the application uptime system, one or more end user incident reports including an incident identifier, a start time of the incident, and a stop time of the incident,
collecting, by the application uptime system, one or more development system incident reports linked to the one or more end user incident reports,
determining, by the application uptime system, at least one end user metric for the application,
generating, by the application uptime system, one or more user interface views based on the at least one end user metric for the application, and
causing to be presented the one or more user interface views.
2. The computer-implemented method of claim 1 further comprising:
receiving, by the application uptime system, a first external trigger that is indicative of a change to the application hosted on a cloud platform, wherein the change comprises a new software version for the application, a patch for the application, and/or a fix for the application.
3. The computer-implemented method of claim 2 , wherein the monitoring is in response to the first external trigger being received by the application uptime system.
4. The computer-implemented method of claim 1 , wherein a successful execution of the application is based in part on whether an incident is reported for the application.
5. The computer-implemented method of claim 1 , wherein when the application does not cause the incident, the execution of the application is considered successful.
6. The computer-implemented method of claim 1 , wherein when the application does cause the incident, the execution of the application is considered unsuccessful.
7. The computer-implemented method of claim 1 , wherein the one or more end user incident reports are collected from a data warehouse coupled to the application uptime system.
8. The computer-implemented method of claim 7 , wherein the one or more end user incident reports are collected using a query based on at least one incident identifier for at least one incident.
9. The computer-implemented method of claim 8 , wherein the one or more development system incident reports are linked to the end user incident reports via the at least one incident identifier.
10. The computer-implemented method of claim 1 , wherein the application uptime system determines the at least one end user metric comprising availability for the application based at least in part on a time associated with the incident being reported to the incident being resolved.
11. A system comprising:
at least one processor; and
at least one memory including instructions which when executed by the at least one processor causes operations comprising:
monitoring, by an application uptime system, whether execution of an application is successful without causing an incident;
in response to the execution of the application being successful without causing the incident, stopping, by the application uptime system, monitoring of the application until an external trigger is received; and
in response to the execution of the application being unsuccessful and causing the incident, the operations further comprising:
collecting, by the application uptime system, one or more end user incident reports including an incident identifier, a start time of the incident, and a stop time of the incident,
collecting, by the application uptime system, one or more development system incident reports linked to the one or more end user incident reports,
determining, by the application uptime system, at least one end user metric for the application,
generating, by the application uptime system, one or more user interface views based on the at least one end user metric for the application, and
causing to be presented the one or more user interface views.
12. The system of claim 11 further comprising:
receiving, by the application uptime system, a first external trigger that is indicative of a change to the application hosted on a cloud platform, wherein the change comprises a new software version for the application, a patch for the application, and/or a fix for the application.
13. The system of claim 12 , wherein the monitoring is in response to the first external trigger being received by the application uptime system.
14. The system of claim 11 , wherein a successful execution of the application is based in part on whether an incident is reported for the application.
15. The system of claim 11 , wherein when the application does not cause the incident, the execution of the application is considered successful.
16. The system of claim 11 , wherein when the application does cause the incident, the execution of the application is considered unsuccessful.
17. The system of claim 11 , wherein the one or more end user incident reports are collected from a data warehouse coupled to the application uptime system.
18. The system of claim 17 , wherein the one or more end user incident reports are collected using a query based on at least one incident identifier for at least one incident.
19. The system of claim 18 , wherein the one or more development system incident reports are linked to the end user incident reports via the at least one incident identifier.
20. A non-transitory computer-readable storage medium including instructions which when executed by at least one processor causes operations comprising:
monitoring, by an application uptime system, whether execution of an application is successful without causing an incident;
in response to the execution of the application being successful without causing the incident, stopping, by the application uptime system, monitoring of the application until an external trigger is received; and
in response to the execution of the application being unsuccessful and causing the incident, the operations further comprising:
collecting, by the application uptime system, one or more end user incident reports including an incident identifier, a start time of the incident, and a stop time of the incident,
collecting, by the application uptime system, one or more development system incident reports linked to the one or more end user incident reports,
determining, by the application uptime system, at least one end user metric for the application,
generating, by the application uptime system, one or more user interface views based on the at least one end user metric for the application, and
causing to be presented the one or more user interface views.