Skip to content

Commit

Permalink
GITBOOK-1015: Suseela's Aug 14 changes
Browse files Browse the repository at this point in the history
  • Loading branch information
Suseela-S authored and gitbook-bot committed Aug 14, 2024
1 parent 275418a commit f5b8d25
Showing 1 changed file with 0 additions and 16 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -26,19 +26,3 @@ In Social Registry (SR), the registrants' data are dynamically populated. There
| APIs | <ul><li>Initiates the periodic task that retrieves a list of Registration IDs that first authenticates with an <strong>OpenG2P API</strong><em>.</em> </li><li>Uses the retrieved list of Registration IDs to call the <strong>Fayda Number API</strong> to get the data from <strong>Fayda API</strong>.</li><li>It updates the Fayda ID and additional information using the <strong>OpenG2P API</strong>.</li><li>At last, data from the response is processed and transformed to update the relevant records with Fayda ID in OpenG2P system.</li></ul> |
| Reliability and consistency | The service's comprehensive **error handling**, **logging systems**, and **continuous operation** **design** ensure trustworthy and consistent data updates. |
| Maintenance | FaydaIDConnector is an essential component of maintaining current registration information by automating these processes and enhancing data accuracy and operational efficiency. |

## Source code

* [https://github.com/OpenG2P/openg2p-eth-nidp](https://github.com/OpenG2P/openg2p-eth-nidp)
* [https://github.com/OpenG2P/openg2p-registry/tree/15.0-develop/g2p\_registry\_rest\_api](https://github.com/OpenG2P/openg2p-registry/tree/15.0-develop/g2p\_registry\_rest\_api)

## **Error handling**&#x20;

* **HTTP Errors**: Handling and logging of HTTP errors during API calls.
* **General Exceptions**: Logging and raising exceptions in the `job_runner` method.

## &#x20;**Logging**&#x20;

The logs are captured in different levels. The various levels and their purposes are given below.

<table><thead><tr><th width="132">Logs</th><th>Purpose</th></tr></thead><tbody><tr><td>Info</td><td>Info log level indicates that something happened, causing the application to enter a certain state. For example, an Info log level in the authorisation API holds information about the user requesting authorisation and whether or not it was approved.</td></tr><tr><td>Debug</td><td>Debug log level provides details on the identified issues or troubleshooting </td></tr><tr><td>Error</td><td>Error log level provides information on the application issue preventing one or more functionalities from properly functioning.</td></tr></tbody></table>

0 comments on commit f5b8d25

Please sign in to comment.