> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-0/monitoring/connectware-metrics.md).

# Connectware Metrics

Connectware exposes metrics in [OpenMetrics](https://openmetrics.io/) format from its key components, so you can monitor connection health, data flow, service state, and authentication activity with the tools you already use, such as Prometheus, Grafana, or Datadog.

Each component serves a `/metrics` endpoint that, for example, a Prometheus server scrapes at a configured interval and stores in its time series database for dashboards and alerting. Metrics carry labels that break down measurements further, for example a connection count by protocol and status, or a message counter by operation type.

## Monitored Components

The following components expose metrics.

| Component                | What the metrics tell you                                                                                                                                                     |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Protocol Mapper          | Whether connections to machines are established, how much data is flowing through endpoints and mappings, and whether node operations are executing correctly.                |
| Service Manager          | How many services are running or disabled, whether recent installations succeeded, how long service enabling takes, and whether dependency resolution failures are occurring. |
| Resource Status Tracking | Whether any services are in a deviated state — that is, not matching their expected configuration.                                                                            |
| Auth Server              | Whether authentication and authorization requests are succeeding, and where failures are occurring by type.                                                                   |

For the full list of individual metrics, their types, labels, and example output for each component, see [Metrics Reference](/2-6-0/monitoring/connectware-metrics/metrics-reference.md).

Broker and NATS expose metrics endpoints as well, but their metrics come from the underlying software rather than from Connectware instrumentation. For Broker metrics, see [Monitoring & Analytics](/2-6-0/broker/cybusmq/configuration/monitoring-and-analytics.md). NATS exposes its metrics through a Prometheus exporter sidecar that is deployed by default and translates NATS metrics into an OpenMetrics-compatible format. Set `nats.metrics.enabled` to `false` to disable it.

## Prometheus Operator Integration

On Kubernetes, the `connectware` and `connectware-agent` Helm charts can create [Prometheus Operator](https://prometheus-operator.dev/docs/developer/getting-started/) `ServiceMonitor` resources for each component, removing the need to maintain a static scrape configuration. See [Configuring Metrics](/2-6-0/cybus-helm-charts/working-with-cybus-helm-charts/metrics.md) for the Helm configuration reference.

## Rate Limiting and Collection Interval

Each metrics endpoint has a built-in rate limiter. When the limit is reached, the endpoint returns the last cached value rather than rejecting the request. Metric values are updated on a fixed collection interval — scraping more frequently than this interval returns the same cached values. The default collection interval is 5,000 milliseconds.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cybus.io/2-6-0/monitoring/connectware-metrics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.