IP Library Granted Patent US 12,355,646
Granted Patent B2
US 12,355,646 · App. 18/523,321 · Granted Jul 8, 2025

Distributed ledger for application health monitoring

Inventors: Somnath Abhishek (Hyderabad, IN); Burramukkala Ravindranath Reddy (Hyderabad, IN); Prasanna Khobragade (Hyderabad, IN); Sai Prakash Garla (Hyderabad, IN)
Assignee: Wells Fargo Bank, N.A.
H04L43/0817H04L12/1895H04L41/0893
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,355,646
App. No.
18/523,321
Granted
Jul 8, 2025
Kind
B2
Abstract

This disclosure describes techniques for application health monitoring using distributed ledger technology in a computing system that includes a plurality of nodes providing application services. For example, the techniques include obtaining health indicators of a particular application service by a computing system. The computing system causes a consensus system that includes a particular node executing the particular application service to vote and verify the status of the node. Based on the verification of the status of the particular node, the consensus system writes an entry to a distributed ledger regarding the status of the particular node. The computing system reads the entry of the distributed ledger and generates a ticket based on the entry. The computing system adds the ticket to a network queue for broadcasting within the computing system.

Claims (53)

1. A method, comprising:

obtaining, by a computing system comprising a plurality of nodes arranged in a network topology, the plurality of nodes providing a plurality of application services, an indication that a particular application service of the plurality of services provided by a particular node of the plurality of nodes is experiencing reduced functionality;

determining, by the computing system, a logical group of nodes of the plurality of nodes that are in communication with the particular application service provided by the particular node, wherein the logical group of nodes includes the particular node;

obtaining, by the computing system, a health indicator for the particular application service from each node of the logical group of nodes;

verifying, by the computing system, that the particular application service provided by the particular node is experiencing reduced functionality based on a determination that health indicators for the particular application service obtained from the logical group of nodes satisfy a consensus threshold; and

broadcasting, by the computing system across the plurality of nodes, an indication of reduced functionality for the particular service provided by the particular node.

2. The method of claim 1 , wherein the logical group of nodes comprises nodes providing one or more application services that have upstream or downstream dependencies with the particular application service provided by the particular node.

3. The method of claim 1 , wherein the logical group of nodes comprises a consensus system, and wherein the consensus threshold comprises a default consensus threshold of the consensus system.

4. The method of claim 1 , further comprising assigning, by the computing system, a criticality of the particular application service based on one or more of:

availability of duplicate application services of the particular application service provided by the plurality of nodes;

a type of application associated with the particular application service; or

a number of dependencies of the particular application service.

5. The method of claim 1 , wherein the logical group of nodes comprises a consensus system, and wherein verifying that the particular application service is experiencing reduced functionality further comprises writing an entry in a distributed ledger maintained by the logical group of nodes that includes the indication of reduced functionality for the particular application service provided by the particular node.

6. The method of claim 5 , wherein the entry in the distributed ledger further includes a criticality indication of the particular application service, wherein the criticality indication comprises one or more of profile information for the particular application service, a priority assigned to the particular application service, a weighting assigned to the particular application service, or a maximum duration of time for which the particular application service can be down.

7. The method of claim 5 , further comprising:

obtaining, by the computing system, a second indication that the particular application service provided by the particular node is experiencing restored functionality;

obtaining, by the computing system, a second health indicator for the particular application service from each node of the logical group of nodes;

verifying, by the computing system, that the particular application service provided by the particular node is experiencing restored functionality based on a determination that second health indicators for the particular application service obtained from the logical group of nodes satisfy the consensus threshold; and

broadcasting, by the computing system across the plurality of nodes, a restoration indication for the particular application service provided by the particular node.

8. The method of claim 7 , wherein the entry in the distributed ledger comprises a first entry, and wherein verifying that the particular application service is experiencing restored functionality further comprises writing a second entry in the distributed ledger maintained by the logical group of nodes that includes the restoration indication for the particular application service provided by the particular node, wherein the second entry is subsequent to the first entry in the distributed ledger.

9. The method of claim 1 , further comprising generating data representative of a dashboard user interface for display on an administrator device associated with the network topology, wherein the dashboard includes the indication of reduced functionality for the particular application service provided by the particular node and an indication of a criticality of the particular application service.

10. The method of claim 1 , wherein broadcasting the indication of reduced functionality for the particular application service provided by the particular node comprises:

generating a support ticket corresponding to the indication of reduced functionality for the particular application service provided by the particular node; and

pushing the support ticket to an event queue, wherein the event queue includes a plurality of support tickets associated with one or more of application services or nodes within the network topology, and wherein the event queue broadcasts a respective support ticket of the plurality of support tickets upon the respective support ticket reaching a top of the queue.

11. The method of claim 10 , wherein each node of the plurality of nodes comprises an application executed on one or more computing devices, and wherein each application provides one or more application services of the plurality of application services.

12. A computing system comprising a plurality of nodes arranged in a network topology, where the plurality of nodes provide a plurality of application services, the computing system comprising:

memory, and

processing circuitry in communication with the memory, the processing circuitry configured to:

obtain an indication that a particular application service of the plurality of application services provided by a particular node of the plurality of nodes is experiencing reduced functionality;

determine a logical group of nodes of the plurality of nodes that are in communication with the particular application service provided by the particular node, wherein the logical group of nodes includes the particular node;

obtain a health indicator for the particular application service from each node of the logical group of nodes;

verify that the particular application service provided by the particular node is experiencing reduced functionality based on a determination that health indicators for the particular application service obtained from the logical group of nodes satisfy a consensus threshold; and

broadcast, across the plurality of nodes, an indication of reduced functionality for the particular service provided by the particular node.

13. The computing system of claim 12 , wherein the logical group of nodes comprises nodes providing one or more application services that have upstream or downstream dependencies with the particular application service provided by the particular node.

14. The computing system of claim 12 , wherein the logical group of nodes comprises a consensus system, and wherein the consensus threshold comprises a default consensus threshold of the consensus system.

15. The computing system of claim 12 , wherein the processing security is further configured to assign a criticality of the particular application service based on one or more of:

availability of duplicate application services of the particular application service provided by the plurality of nodes;

a type of application associated with the particular application service; or

a number of dependencies of the particular application service.

16. The computing system of claim 12 , wherein the logical group of nodes comprises a consensus system, and wherein to verify the that the particular application service is experiencing reduced functionality, the processing circuitry is configured to write an entry in a distributed ledger maintained by the logical group of nodes that includes the indication of reduced functionality for the particular application service provided by the particular node.

17. The computing system of claim 16 , wherein the entry in the distributed ledger further includes a criticality indication of the particular application service, wherein the criticality indication comprises one or more of profile information for the particular application service, a priority assigned to the particular application service, a weighting assigned to the particular application service, or a maximum duration of time for which the particular application service can be down.

18. The computing system of claim 16 , wherein the processing circuitry is further configured to:

obtain a second indication that the particular application service provided by the particular node is experiencing restored functionality;

obtain a second health indicator for the particular application service from each node of the logical group of nodes;

verify that the particular application service provided by the particular node is experiencing restored functionality based on a determination that second health indicators for the particular application service obtained from the logical group of nodes satisfy the consensus threshold; and

broadcast, across the plurality of nodes, a restoration indication for the particular service provided by the particular node.

19. The computing system of claim 12 , wherein the processing circuitry is further configured to generate data representative of a dashboard user interface for display on an administrator device associated with the network topology, wherein the dashboard includes the indication of reduced functionality for the particular application service provided by the particular node and an indication of a criticality of the particular application service.

20. Non-transitory computer-readable media comprising instructions that, when executed, cause processing circuitry of a computing system including a plurality of nodes arranged in a network topology to:

obtain an indication that a particular application service of a plurality of application services provided by a particular node of the plurality of nodes is experiencing reduced functionality;

determine a logical group of nodes of the plurality of nodes that are in communication with the particular application service provided by the particular node, wherein the logical group of nodes includes the particular node;

obtain a health indicator for the particular application service from each node of the logical group of nodes;

verify that the particular application service provided by the particular node is experiencing reduced functionality based on a determination that health indicators for the particular application service obtained from the logical group of nodes satisfy a consensus threshold; and

broadcast, across the plurality of nodes, an indication of reduced functionality for the particular service provided by the particular node.

Assignments (2)
REQUEST FOR ADDRESS CHANGE Recorded Dec 5, 2025
From: WELLS FARGO BANK, N.A.
To: WELLS FARGO BANK, N.A.
Reel/Frame 073896/0195 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 28, 2023
From: ABHISHEK, SOMNATH; REDDY, BURRAMUKKALA RAVINDRANATH; KHOBRAGADE, PRASANNA; GARLA, SAI PRAKASH
To: WELLS FARGO BANK, N.A.
Reel/Frame 065972/0615 →
Continuity (1)
Related Publication 20250175403A1 · May 29, 2025
References Cited (32)
US 7210145B2 · Srinivasan · 2007 [cited by applicant]
US 7512841B2 · Walker et al. · 2009 [cited by applicant]
US 7734960B2 · Mandal · 2010 [cited by applicant]
US 8605601B2 · Isaksson et al. · 2013 [cited by applicant]
US 9104543B1 · Cavanagh et al. · 2015 [cited by applicant]
US 9772920B2 · Kizhakkiniyil et al. · 2017 [cited by applicant]
US 9823641B2 · Senda et al. · 2017 [cited by applicant]
US 10075384B2 · Shear et al. · 2018 [cited by applicant]
US 11003645B1 · Thompson et al. · 2021 [cited by applicant]
US 11030248B2 · Borochoff et al. · 2021 [cited by applicant]
US 11146640B2 · Rath et al. · 2021 [cited by applicant]
US 11238448B1 · Narayanan · 2022 [cited by examiner]
US 11438250B2 · Venkatesh et al. · 2022 [cited by applicant]
US 20060087976A1 · Rhodes et al. · 2006 [cited by applicant]
US 20170295232A1 · Curtis · 2017 [cited by examiner]
US 20190089611A1 · Kondalam et al. · 2019 [cited by applicant]
US 20190149418A1 · Bertsche · 2019 [cited by examiner]
US 20190318338A1 · Verma · 2019 [cited by examiner]
US 20200389495A1 · Crabtree et al. · 2020 [cited by applicant]
US 20210144517A1 · Bernat et al. · 2021 [cited by applicant]
US 20220035693A1 · Jiang · 2022 [cited by examiner]
US 20220350734A1 · Coutinho Moraes et al. · 2022 [cited by applicant]
US 20220398173A1 · Rodriguez Bravo · 2022 [cited by examiner]
CN 111835872B · 2020 [cited by applicant]
JP 3322302B2 · 2002 [cited by applicant]
WO 200545559A2 · 2005 [cited by applicant]
WO 2007123527A1 · 2007 [cited by applicant]
WO 2021206704A1 · 2021 [cited by applicant]
Aggour et al., “Colt: concept lineage tool for data flow metadata capture and analysis”, Proceedings of the VLDB Endowment, vol. 10, No. 12, VLDB Endowment, Aug. 1, 2017, pp. 1790-1801. [cited by applicant]
Medvedev et al., “Gaining Insights into Conceptual Models: A Graph-Theoretic Querying Approach”, Applied Sciences, vol. 11, No. 2, Jan. 14, 2021, 29 pp. [cited by applicant]
Jahromi et al., “Towards Application-Aware Networking: ML-Based End-to-End Application KPI/QoE Metrics Characterization in SDN”, Tenth International Conference on Ubiquitous and Future Networks, IEEE, Jul. 3, 2018, 6 pa… [cited by applicant]
Benet et al., “IPFS is an open system to manage data without a central server”, Github, Feb. 28, 2024, 2 pp., URL: https://github.com/ipfs/ipfs. [cited by applicant]