layout | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The Reporting Framework is an infrastructure to make database data available in searchable indexes for efficient slicing and dicing of data and real-time monitoring with visualization and reports. The framework utilizes open-source components to achieve this data pipeline and visualization capabilities.
{% embed url="https://miro.com/app/board/uXjVKY0ZdOQ=/?share_link_id=736231944012" %}
Postgres WAL contains events on the database, specifically, changes to any table fields. These events are read by Debezium and pushed to Kafka Topics. Using a connector the fields are further pushed into OpenSearch indexes. These indexes may be searched by APIs or consumed by OpenSearch Dashboards for visualization.
The salient features of the framework are the following:
Features | Benefits |
---|---|
Searchable indexes in OpenSearch |
|
OpenSearch Dashboards |
|
Authentication and authorisation using Keycloak |
|
PII data not available for search* |
|
{% hint style="info" %} * As a highly recommended practice PII data is not shunted to the search indexes, however, the framework does not impose any restriction as such. {% endhint %}
Refer to Installation Guide and Post Installation Check.
- Pick the URL provided during the installation of the Helm chart of the module (like SR, PBMS)
- Add Keycloak roles to the user who is accessing the dashboard (as given here).
- Confirm that the number of indexed records in OpenSearch matches the number of rows in the DB (guide TBD). This check confirms that the reporting pipeline is working fine.