Granted Patent B2

US 12,645,562 · App. 17/656,529 · Granted Jun 2, 2026

Inventors: Sandipan Biswas (Kolkata, IN); Mandeep Kumawat (Bengaluru, IN); Abhishek Gupta (Kolkata, IN)

Assignees: Atlassian Pty, Ltd.; ATLASSIAN US, INC.

G06F11/3612G06F11/3616G06F11/3698

Abstract

Claims (71)

1 . An apparatus for generating service health status data objects associated with one or more software service data objects in a cloud-based software service system, the apparatus comprising at least one processor and at least one non-transitory memory comprising program code, the at least one non-transitory memory and the program code being configured to, with the at least one processor, cause the apparatus to at least:

receive one or more metric-based alert data objects associated with the cloud-based software service system from a service system metric monitoring platform, wherein the service system metric monitoring platform is external to the cloud-based software service system;

retrieve, from a service health status monitoring data repository, one or more metric-based rule data objects comprising user-defined mapping metadata that defines a plurality of mappings between the one or more metric-based alert data objects and the one or more software service data objects;

generate a service health status data object associated with a software service data object of the one or more software service data objects by:

traversing the one or more metric-based alert data objects to extract system-monitored metric metadata,

establishing a connection between at least one metric-based alert data object of the one or more metric-based alert data objects and the software service data object that is not provided by the service system metric monitoring platform by programmatically correlating the at least one metric-based alert data object with the software service data object based at least in part on the system-monitored metric metadata and the user-defined mapping metadata, and

generating service health status metadata of the service health status data object based on the at least one metric-based alert data object, wherein the service health status metadata indicates a software service health level of the software service data object; and

cause rendering of a health status monitoring user interface on a client device, wherein the health status monitoring user interface comprises a service health status user interface object corresponding to the software service data object based at least in part on the service health status data object and an impacted services user interface button; and

in response to receiving a user selection input of the impacted services user interface button, cause rendering of a service dependency graph user interface on the client device.

2 . The apparatus of claim 1 , wherein the one or more metric-based alert data objects comprise at least one of one or more system alert data objects or one or more system metric data objects.

3 . The apparatus of claim 1 , wherein the user-defined mapping metadata comprises metric-to-service mapping indicator and metric-to-health mapping indicator.

4 . The apparatus of claim 3 , wherein the metric-to-service mapping indicator comprises one or more software service identification criteria and one or more software service data object identifiers, wherein each of the one or more software service identification criteria corresponds to one of the one or more software service data object identifiers, wherein each of the one or more software service data object identifiers is associated with one of the one or more software service data objects.

5 . The apparatus of claim 4 , wherein, when programmatically relating the at least one metric-based alert data objects with the software service data object, the at least one non-transitory memory and the program code are configured to, with the at least one processor, cause the apparatus to:

determine whether the system-monitored metric metadata satisfies a software service identification criterion of the one or more software service identification criteria; and

in response to determining that the system-monitored metric metadata satisfies the software service identification criterion:

determine a software service data object identifier corresponds to the software service identification criterion; and

select the software service data object corresponding to the software service data object identifier.

6 . The apparatus of claim 5 , wherein the metric-to-health mapping indicator comprises one or more software service health criteria and one or more software service health level identifiers, wherein each of the one or more software service health criteria corresponds to one of the one or more software service health level identifiers, wherein each of the one or more software service health level identifiers indicates a corresponding software service health level.

7 . The apparatus of claim 6 , wherein, when generating the service health status metadata of the service health status data object, the at least one non-transitory memory and the program code are configured to, with the at least one processor, cause the apparatus to:

determine whether the system-monitored metric metadata satisfies a software service health criterion of the one or more software service health criteria; and

in response to determining that the system-monitored metric metadata satisfies the software service health criterion:

determine a software service health level identifier corresponds to the software service health criterion; and

determine the service health status metadata based at least in part on the software service health level identifier.

8 . The apparatus of claim 1 , wherein the at least one non-transitory memory and the program code are configured to, with the at least one processor, cause the apparatus to:

retrieve a service dependency data object associated with the cloud-based software service system, wherein the service dependency data object comprises service dependency metadata associated with the one or more software service data objects;

determine at least one related software service data object associated with the software service data object based at least in part on the service dependency metadata of the service dependency data object;

determine at least one related service health status data object associated with the at least one related software service data object, wherein the at least one related service health status data object indicates at least one related software service health level of the at least one related software service data object; and

adjust, based at least in part on the at least one related service health status data object, the service health status metadata of the service health status data object.

9 . The apparatus of claim 8 , wherein, when adjusting the service health status metadata of the service health status data object based at least in part on the at least one related service health status data object, the at least one non-transitory memory and the program code are configured to, with the at least one processor, cause the apparatus to:

determine whether the at least one related service health status data object indicates a healthy status or an unhealthy status.

10 . The apparatus of claim 9 , wherein the at least one non-transitory memory and the program code are configured to, with the at least one processor, cause the apparatus to:

in response to determining that the at least one related service health status data object indicates the unhealthy status, decrease the software service health level associated with the software service data object.

11 . The apparatus of claim 9 , wherein the at least one non-transitory memory and the program code are configured to, with the at least one processor, cause the apparatus to:

in response to determining that the at least one related service health status data object indicates the healthy status, increase the software service health level associated with the software service data object.

12 . A computer-implemented method for generating service health status data objects associated with one or more software service data objects in a cloud-based software service system, comprising:

receiving one or more metric-based alert data objects associated with the cloud-based software service system from a service system metric monitoring platform, wherein the service system metric monitoring platform is external to the cloud-based software service system;

retrieving, from a service health status monitoring data repository, one or more metric- based rule data objects comprising user-defined mapping metadata that defines a plurality of mappings between the one or more metric-based alert data objects and the one or more software service data objects;

generating a service health status data object associated with a software service data object of the one or more software service data objects by:

traversing the one or more metric-based alert data objects to extract system-monitored metric metadata,

establishing a connection between at least one metric-based alert data object of the one or more metric-based alert data objects and the software service data object that is not provided by the service system metric monitoring platform by programmatically correlating the at least one metric-based alert data object with the software service data object based at least in part on the system-monitored metric metadata and the user-defined mapping metadata, and

generating service health status metadata of the service health status data object based on the at least one metric-based alert data object, wherein the service health status metadata indicates a software service health level of the software service data object; and

causing rendering of a health status monitoring user interface on a client device, wherein the health status monitoring user interface comprises a service health status user interface object corresponding to the software service data object based at least in part on the service health status data object and an impacted services user interface button; and

in response to receiving a user selection input of the impacted services user interface button, cause rendering of a service dependency graph user interface on the client device.

13 . The computer-implemented method of claim 12 , wherein the one or more metric-based alert data objects comprise at least one of one or more system alert data objects or one or more system metric data objects.

14 . The computer-implemented method of claim 12 , wherein the user- defined mapping metadata comprises metric-to-service mapping indicator and metric-to-health mapping indicator.

15 . The computer-implemented method of claim 14 , wherein the metric-to- service mapping indicator comprises one or more software service identification criteria and one or more software service data object identifiers, wherein each of the one or more software service identification criteria corresponds to one of the one or more software service data object identifiers, wherein each of the one or more software service data object identifiers is associated with one of the one or more software service data objects.

16 . The computer-implemented method of claim 15 , wherein, when programmatically relating the at least one metric-based alert data objects with the software service data object, the computer-implemented method further comprises:

determining whether the system-monitored metric metadata satisfies a software service identification criterion of the one or more software service identification criteria; and

in response to determining that the system-monitored metric metadata satisfies the software service identification criterion:

determining a software service data object identifier corresponds to the software service identification criterion; and

selecting the software service data object corresponding to the software service data object identifier.

17 . The computer-implemented method of claim 16 , wherein the metric-to- health mapping indicator comprises one or more software service health criteria and one or more software service health level identifiers, wherein each of the one or more software service health criteria corresponds to one of the one or more software service health level identifiers, wherein each of the one or more software service health level identifiers indicates a corresponding software service health level.

18 . The computer-implemented method of claim 17 , wherein, when generating the service health status metadata of the service health status data object, the computer-implemented method further comprises:

determining whether the system-monitored metric metadata satisfies a software service health criterion of the one or more software service health criteria; and

in response to determining that the system-monitored metric metadata satisfies the software service health criterion:

determining a software service health level identifier corresponds to the software service health criterion; and

determining the service health status metadata based at least in part on the software service health level identifier.

19 . The computer-implemented method of claim 12 , further comprising:

retrieving a service dependency data object associated with the cloud-based software service system, wherein the service dependency data object comprises service dependency metadata associated with the one or more software service data objects;

determining at least one related software service data object associated with the software service data object based at least in part on the service dependency metadata of the service dependency data object;

determining at least one related service health status data object associated with the at least one related software service data object, wherein the at least one related service health status data object indicates at least one related software service health level of the at least one related software service data object; and

adjusting, based at least in part on the at least one related service health status data object, the service health status metadata of the service health status data object.

20 . A computer program product for generating service health status data objects associated with one or more software service data objects in a cloud-based software service system, the computer program product comprising at least one non-transitory computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising an executable portion configured to:

receive one or more metric-based alert data objects associated with the cloud-based software service system from a service system metric monitoring platform, wherein the service system metric monitoring platform is external to the cloud-based software service system;

retrieve, from a service health status monitoring data repository, one or more metric-based data objects comprising user-defined mapping metadata that defines a plurality of mappings between the one or more metric-based alert data objects and the one or more software service data objects;

generate a service health status data object associated with a software service data object of the one or more software service data objects by:

traversing the one or more metric-based alert data objects to extract system-monitored metric metadata,

establishing a connection between at least one metric-based alert data object of the one or more metric-based alert data objects and the software service data object that is not provided by the service system metric monitoring platform by programmatically correlating the at least one metric-based alert data object with the software service data object based at least in part on the system-monitored metric metadata and the user-defined mapping metadata, and

generating service health status metadata of the service health status data object based on the at least one metric-based alert data object, wherein the service health status metadata indicates a software service health level of the software service data object; and

cause rendering of a health status monitoring user interface on a client device, wherein the health status monitoring user interface comprises a service health status user interface object corresponding to the software service data object based at least in part on the service health status data object and an impacted services user interface button; and

in response to receiving a user selection input of the impacted services user interface button, cause rendering of a service dependency graph user interface on the client device.

Assignments (2)

Continuity (1)

References Cited (23)