Monitor the health of the SystemLink Enterprise v2 Routine Service using OpenTelemetry metrics and Prometheus metrics.

Introduced in May 2025

For information on the metrics emitted by the v2 Routine Service and related dependencies, refer to the following tables.
Note You can deploy and configure the OpenTelemetry collector to expose all OpenTelemetry metrics as Prometheus metrics. Exposing these metrics to Prometheus allows you to view the metrics in a tool such as Grafana.

v2 Routine Service

KPI? Metric Type Description Labels
Yes ni.routine.routines.count Counter

The number of routines.

Use this metric to understand how many routines the service is managing.

The v2 Routine Service limits the number of routines that the service manages per organization to a configurable limit. The default limit is 1000. To adjust the limit, modify routineservice.v2.routineLimit in the Helm values file of the deployment.

NI recommends that you configure a warning alert for when the service approaches the routine limit. For example, you can receive an alert when the service reaches 700 routines.

NI also recommends an alert for when the service reaches the routine limit.

 ni.org: A value for each org in the deployment.

v2 Routine Service Dependencies

To learn about other available performance metrics, refer to the documentation for the following v2 Routine Service dependencies.

Dependency Where to Find Information
ASP.NET

For a list of the metrics provided by ASP.NET, refer to ASP.NET Core Metrics and ASP.NET Runtime Metrics.
Kubernetes

For a list of the metrics provided by Kubernetes, refer to the Kubernetes Metrics Reference and the kube-state-metrics Documentation on GitHub.
MongoDB

For more information on MongoDB, refer to the How to Monitor MongoDB Documentation.
RabbitMQ

For more information on RabbitMQ, refer to the How to Monitor RabbitMQ Documentation.