In the BRIX On-Premises Enterprise package, it is possible to analyze elma365_telemetry_* metrics:
- In the internal performance report available in the BRIX interface.
- By exporting metrics to the standard Prometheus storage and visualizing them as dashboards in Grafana.
Internal reporting and metrics export to external storage are configured independently of each other. If they are disabled at the same time, the system performance diagnostic data is not collected.
Read more on how to configure an internal report in the Performance report article.
In this article, we will consider exporting system performance data to the Prometheus storage. You can export the following metrics:
elma365_telemetry_http_request_duration_milliseconds_bucketfor web request execution time.elma365_telemetry_script_execution_duration_milliseconds_bucketfor server script execution time, excluding waiting in queue.elma365_telemetry_script_execution_duration_with_queuefor total server script execution time, including waiting in queue.elma365_telemetry_sql_query_duration_milliseconds_bucketfor database query execution time.
To configure the export of metrics from the performance report to the Prometheus storage, follow these steps:
- Install the monitoring tools Prometheus and Grafana if they are not already installed. Skip this step if they are already set up.
- In the
values-elma365.yamlconfiguration file, enable monitoring parameters. During the setup, set the value for theglobal.monitoring.lowcode.metricExportEnabledparameter to thetruevalue.
Once metrics export is enabled, diagnostic data is collected and exported continuously.
Found a typo? Select it and press Ctrl+Enter to send us feedback