RDM Monitoring Metrics

The following article provides a list of available monitoring metrics for RDM.

Metric Metric type Description Labels

rdm_number_of_active_sqlStatements_running

Gauge

The number of SQL statements in progress.

[]

rdm_number_of_active_methods_running

Gauge

The number of methods in progress.

[]

rdm_number_of_acquired_locks

Gauge

The number of required locks.

[]

rdm_number_of_waiting_locks

Gauge

The number of requested but not acquired locks.

[]

ataccama_one_business_ready

Gauge

The indicator of whether RDM Web App is business ready, where 0 means that the application is starting up and is not yet initialized. The value of 1 covers all other states (for example, the configuration is being processed or is invalid, or the application is ready for use).

To get more details about the application state, use ataccama_one_rdm_application_state.

[]

ataccama_one_rdm_keycloak_load_realm_duration

Timer

How long it took to load all RDM users with their roles from Keycloak.

[]

ataccama_one_rdm_query_duration

Timer with buckets

The query execution duration.

Bucket ’le’ (less or equal) values: 100ms, 500ms, 2s, 10s.

[’le’]

ataccama_one_rdm_query_fail

Counter

The number of failed query executions. Complementary to ataccama_one_rdm_query_duration.

[]

ataccama_one_rdm_soap_downloader_durations

Timer

The duration of SOAP calls to the RDM server for different actions defined in RDM configuration. The ‘action’ label value is taken from soapAction in validators.xml.

[’action’]

ataccama_one_rdm_soap_downloader_fail

Counter

The number of failed SOAP calls to the RDM server. Complementary to ataccama_one_rdm_soap_downloader_durations.

[’action’]

ataccama_one_rdm_semaphore_state

Gauge

The state of internal RDM locks for entities and system objects. Possible state values are 0 (released), 0.5 (requested), 1 (locked).

The ‘lock’ label value is the name of the locked object.

Not all entities and system classes which are being locked are monitored.

[’lock’]

ataccama_one_rdm_semaphore_acquire_timeout

Counter

The number of times acquiring lock failed on timeout. Complementary to ataccama_one_rdm_semaphore_state.

[’lock’]

ataccama_one_rdm_method_duration

Timer

The duration of administration, security, and data service method calls. The ‘class’ label value is the service class name while the ‘action_type’ label value is the method name.

[’class’, ’action_type’]

ataccama_one_rdm_method_fail

Counter

The number of failed method calls. Complementary to ataccama_one_rdm_method_duration.

[’class’, ’action_type’]

ataccama_one_rdm_task_duration

Timer with buckets

The duration of finished RDM background operations. Bucket ’le’ (less or equal) values: 1s, 5s, 10s, 60s.

[]

ataccama_one_rdm_task_fail

Counter

The number of failed RDM background operations.

[]

ataccama_one_rdm_entity_count

Gauge

The number of entity records. Collected once per day (configurable).

The ‘type’ label value is TABLE or VIEW. The ’name’ is the entity name and ’state’ is the record status (CONFIRMED, EDIT, or ALL_HISTORY).

ALL_HISTORY is not available for VIEW type.

[’type’, ’name’, ’state’]

ataccama_one_rdm_config_entity_count

Gauge

The number of entities (tables, views, datasets) based on the last successfully applied configuration. You can use this to determine the number of entities before any rows are added to specific entities.

[]

rdm_total_number_of_background_tasks

Gauge

The number of RDM background operations in progress.

[]

ataccama_one_rdm_http_request

Counter

The number of HTTP requests the RDM Web App received. Requests made to files are not counted.

The ’uri’ label value identifies the target service, servlet, or resource.

[’uri’]

ataccama_one_rdm_user_permissions

Gauge

The number of users with any type of edit permission allowing them to change data (edit, delete, confirm). It also includes users who have edit permissions only on the column level.

[]

ataccama_one_rdm_application_state

Gauge

A number describing the application state. Possible values:

1: STARTING. The application core is starting.
2: WAITING_FOR_ACTION. The application is waiting for user action. Typically, this means you need to review and approve or reject a model proposal.
3: PROCESSING_MODEL. The application is processing or updating the model.
4: STOPPING_MODEL. The application is stopping the model deployment. This is a temporary state.
5: FAILURE. The application failed to start or deploy the model.
6: SUCCESS. The application has started and the model is deployed.

[]

Was this page useful?