IP Library › Granted Patent US 12,493,507
Granted Patent B2
US 12,493,507 · App. 18/509,700 · Granted Dec 9, 2025

Granular monitoring and alerting system for microservices

Inventors: Sreekanth Kozhisseri Pattath (Kerala, IN); Sreeram V (Kerala, IN); Sudheernath Reddy Kaipa (Andhra Pradesh, IN); Wei Li (Shanghai, CN); Xiangjun Xiao (Shanghai, CN); Vidhya K (Bangalore, IN)
Assignee: SAP SE
G06F11/0766G06F11/3006G06F11/302G06F11/3409G06F11/3616
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,493,507
App. No.
18/509,700
Granted
Dec 9, 2025
Kind
B2
Abstract

A computer-implemented method may comprise obtaining thresholds for metrics for microservices, injecting metadata comprising the thresholds for each microservice into a pod within which the microservice is running, obtaining the metrics for the microservices, obtaining the corresponding metadata from the pod within which each microservice is running, determining that one of the thresholds for one of the microservices has been violated using the metadata of the microservice obtained from the corresponding pod of the microservice and the corresponding set of metrics for the microservice, and sending an alert to an electronic destination based on the determining that the threshold for the microservice has been violated. The alert may indicate that the threshold for the microservice has been violated.

Claims (49)

1 . A computer-implemented method comprising:

for each one of a plurality of microservices, obtaining a corresponding set of one or more thresholds for a corresponding set of one or more metrics of the microservice;

for each one of the plurality of microservices, injecting corresponding metadata into a pod within which the microservice is running, the corresponding metadata comprising the corresponding set of one or more thresholds for the microservice, wherein the injecting of the corresponding metadata comprises:

intercepting, by an admission controller, a request sent to a server of a container orchestration system, the request comprising a request to create a new pod or a request to update an existing pod;

receiving, by a webhook server, the intercepted request from the admission controller; and

in response to the receiving of the intercepted request, injecting, by a webhook of the webhook server, the corresponding metadata into the pod within which the microservice is running by mounting the corresponding metadata in a file system of the pod;

obtaining the corresponding set of one or more metrics for each one of the plurality of microservices;

for one of the plurality of microservices, obtaining the corresponding metadata from the pod within which the microservice is running;

determining that one of the thresholds in the corresponding set of one or more thresholds for the one of the plurality of microservices has been violated using the corresponding metadata of the microservice obtained from the pod of the microservice and the corresponding set of one or more metrics for the one of the plurality of microservices; and

sending an alert to an electronic destination based on the determining that the one of the thresholds in the corresponding set of one or more thresholds for the one of the plurality of microservices has been violated, the alert indicating that the one of the thresholds for the one of the plurality of microservices has been violated.

2 . The computer-implemented method of claim 1 , wherein at least two of the plurality of microservices are running within a same pod as each other, the at least two of the plurality of microservices running within separate containers from each other.

3 . The computer-implemented method of claim 1 , wherein the determining that the one of the thresholds has been violated comprises determining that one of the one or more thresholds has been exceeded based on one of the metrics in the corresponding set of one or more metrics for the one of the plurality of microservices.

4 . The computer-implemented method of claim 1 , wherein the corresponding set of one or more metrics for the one of the plurality of microservices comprises one or more metrics of usage of one or more resources of the pod within which the one of the plurality of microservices is running, the one or more resources of the pod comprising a central processing unit, a memory, or a network.

5 . The computer-implemented method of claim 1 , wherein the corresponding metadata comprises one or more key-value pairs mapping the corresponding set of one or more metrics for the one of the plurality of microservices to the corresponding set of one or more thresholds for the one of the plurality of microservices.

6 . The computer-implemented method of claim 1 , wherein the sending of the alert to the electronic destination comprises causing the alert to be displayed on a computing device.

7 . The computer-implemented method of claim 1 , wherein the alert comprises an identification of the pod on which the one of the plurality of microservices is running and an identification of the one of the thresholds that had been violated.

8 . A system comprising:

at least one hardware processor; and

a non-transitory computer-readable medium storing executable instructions that, when executed, cause the at least one hardware processor to perform computer operations comprising:

for each one of a plurality of microservices, obtaining a corresponding set of one or more thresholds for a corresponding set of one or more metrics of the microservice;

for each one of the plurality of microservices, injecting corresponding metadata into a pod within which the microservice is running, the corresponding metadata comprising the corresponding set of one or more thresholds for the microservice, wherein the injecting of the corresponding metadata comprises:

intercepting, by an admission controller, a request sent to a server of a container orchestration system, the request comprising a request to create a new pod or a request to update an existing pod;

receiving, by a webhook server, the intercepted request from the admission controller; and

in response to the receiving of the intercepted request, injecting, by a webhook of the webhook server, the corresponding metadata into the pod within which the microservice is running by mounting the corresponding metadata in a file system of the pod;

obtaining the corresponding set of one or more metrics for each one of the plurality of microservices;

for one of the plurality of microservices, obtaining the corresponding metadata from the pod within which the microservice is running;

determining that one of the thresholds in the corresponding set of one or more thresholds for the one of the plurality of microservices has been violated using the corresponding metadata of the microservice obtained from the pod of the microservice and the corresponding set of one or more metrics for the one of the plurality of microservices; and

sending an alert to an electronic destination based on the determining that the one of the thresholds in the corresponding set of one or more thresholds for the one of the plurality of microservices has been violated, the alert indicating that the one of the thresholds for the one of the plurality of microservices has been violated.

9 . The system of claim 8 , wherein at least two of the plurality of microservices are running within a same pod as each other, the at least two of the plurality of microservices running within separate containers from each other.

10 . The system of claim 8 , wherein the determining that the one of the thresholds has been violated comprises determining that one of the one or more thresholds has been exceeded based on one of the metrics in the corresponding set of one or more metrics for the one of the plurality of microservices.

11 . The system of claim 8 , wherein the corresponding set of one or more metrics for the one of the plurality of microservices comprises one or more metrics of usage of one or more resources of the pod within which the one of the plurality of microservices is running, the one or more resources of the pod comprising a central processing unit, a memory, or a network.

12 . The system of claim 8 , wherein the corresponding metadata comprises one or more key-value pairs mapping the corresponding set of one or more metrics for the microservice to the corresponding set of one or more thresholds for the one of the plurality of microservices.

13 . The system of claim 8 , wherein the sending of the alert to the electronic destination comprises causing the alert to be displayed on a computing device.

14 . The system of claim 8 , wherein the alert comprises an identification of the pod on which the one of the plurality of microservices is running and an identification of the one of the thresholds that had been violated.

15 . A non-transitory machine-readable storage medium tangibly embodying a set of instructions that, when executed by at least one hardware processor, causes the at least one hardware processor to perform computer operations comprising:

for each one of a plurality of microservices, obtaining a corresponding set of one or more thresholds for a corresponding set of one or more metrics of the microservice;

for each one of the plurality of microservices, injecting corresponding metadata into a pod within which the microservice is running, the corresponding metadata comprising the corresponding set of one or more thresholds for the microservice, wherein the injecting of the corresponding metadata comprises:

intercepting, by an admission controller, a request sent to a server of a container orchestration system, the request comprising a request to create a new pod or a request to update an existing pod;

receiving, by a webhook server, the intercepted request from the admission controller; and

in response to the receiving of the intercepted request, injecting, by a webhook of the webhook server, the corresponding metadata into the pod within which the microservice is running by mounting the corresponding metadata in a file system of the pod;

obtaining the corresponding set of one or more metrics for each one of the plurality of microservices;

for one of the plurality of microservices, obtaining the corresponding metadata from the pod within which the microservice is running;

determining that one of the thresholds in the corresponding set of one or more thresholds for the one of the plurality of microservices has been violated using the corresponding metadata of the microservice obtained from the pod of the microservice and the corresponding set of one or more metrics for the one of the plurality of microservices; and

sending an alert to an electronic destination based on the determining that the one of the thresholds in the corresponding set of one or more thresholds for the one of the plurality of microservices has been violated, the alert indicating that the one of the thresholds for the one of the plurality of microservices has been violated.

16 . The non-transitory machine-readable storage medium of claim 15 , wherein the determining that the one of the thresholds has been violated comprises determining that one of the one or more thresholds has been exceeded based on one of the metrics in the corresponding set of one or more metrics for the one of the plurality of microservices.

17 . The non-transitory machine-readable storage medium of claim 15 , wherein the corresponding set of one or more metrics for the one of the plurality of microservices comprises one or more metrics of usage of one or more resources of the pod within which the microservice is running, the one or more resources of the pod comprising a central processing unit, a memory, or a network.

18 . The non-transitory machine-readable storage medium of claim 15 , wherein the corresponding metadata comprises one or more key-value pairs mapping the set of one or more metrics for the microservice to the set of one or more thresholds for the microservice.

19 . The non-transitory machine-readable storage medium of claim 15 , wherein at least two of the plurality of microservices are running within a same pod as each other, the at least two of the plurality of microservices running within separate containers from each other.

20 . The non-transitory machine-readable storage medium of claim 15 , wherein the sending of the alert to the electronic destination comprises causing the alert to be displayed on a computing device.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 15, 2023
From: PATTATH, SREEKANTH KOZHISSERI; V, SREERAM; KAIPA, SUDHEERNATH REDDY; LI, WEI; XIAO, XIANGJUN; K, VIDHYA
To: SAP SE
Reel/Frame 065570/0434 →
Continuity (1)
Related Publication 20250156258A1 · May 15, 2025
References Cited (9)
US 9471345B2 · Jain · 2016 [cited by applicant]
US 11347622B1 · Agarwal · 2022 [cited by examiner]
US 11563636B1 · Kairali · 2023 [cited by examiner]
US 20080163270A1 · Mitrov · 2008 [cited by applicant]
US 20150089474A1 · Jain · 2015 [cited by applicant]
US 20220100591A1 · Kohn · 2022 [cited by applicant]
US 20230198959A1 · Martinez-Spessot · 2023 [cited by examiner]
US 20240305541A1 · Singarayan · 2024 [cited by examiner]
US 20240386130A1 · Bruce · 2024 [cited by examiner]