Registry analytical reporting subsystem

Viewing and configuring dashboards with registry data.

Viewing and analyzing dashboards with registry audit events log data.

Redash server: The Redash server processes user requests, manages user authentication and authorization, and provides the Redash web interface and administrative API. Users interact with Redash through the web interface, while the regulations and registry deployment subsystems use the API. The Redash server interacts with other services asynchronously using RQ (Redis Queue) to handle requests and receive data.

Queue processors: Redash uses worker processes to handle tasks from the queue asynchronously. Queue processors perform tasks such as querying the data sources, generating query results, and sending query execution updates to the user interface.

Redash DB: Redash uses a PostgreSQL relational database as its primary metadata store. The database stores metadata related to users, requests, dashboards, and visualizations. It also stores request results and cached data. Redash services interact with the database to obtain and store the necessary information.

Redis queue: The Redis queue database is an in-memory data store that Redash uses to manage shared query execution locks and distribute tasks between worker processes.

When users interact with the Redash web interface, their requests are processed by the Redash server. The server authenticates the user via the Users and roles management subsystem, verifies the request, and interacts with the appropriate services based on the user’s actions.

When a user executes a request, the server receives the request and sends it to the workflow through the Redis queue. A Redash worker accepts the task and executes the request asynchronously while periodically updating the state of the request and sending updates to the UI.

Once the request is processed, the workflow saves the final result, and the server receives it to display to the user.

Redash

Python

PostgreSQL

Redis

Helm