> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Agent home for Datum, with what it is, pricing, and how to act: https://agents.datum.net
> If you can only fetch URLs: read https://www.datum.net/docs/llms.txt in full and open the most specific page for the task. Commands, limits, and field paths are on task, operations, and limits pages, not on section overviews. Pages described as "Documentation is coming soon" are placeholders.
> If you have a shell or can save files: download https://www.datum.net/docs/llms-full.txt (every page, about 740 KB) once and search it with grep, instead of fetching pages one at a time.
> datumctl describes itself: `datumctl api-resources` lists resource types and `datumctl explain <resource>` shows a schema. To act on live resources, use Datum MCP or datumctl. To search the docs, use the Docs MCP server at https://www.datum.net/docs/mcp.

# Connectors observability

> See the traffic that reaches your Connectors through a load balancer, and the metrics and logs Datum publishes for it.

This page covers how to see the traffic your [Connectors](/docs/connectors/overview.md) carry. Datum is still building Connectors, and more detail is on the way.

## Traffic through a load balancer

Today, a Connector receives traffic through an [Application Load Balancer](/docs/alb/overview.md) whose route uses a `connector` backend. Every request it carries is measured and logged by that load balancer, so you observe a Connector through the load balancers that use it.

In the [Cloud Portal](https://cloud.datum.net), each Connector shows a request-rate chart that adds up the traffic from every load balancer that routes to it.

### Metrics

Use the [ALB traffic and latency metrics](/docs/alb/observability.md#traffic-and-latency), selected by the name of each load balancer that routes to your Connector. For example, to see requests per second through one load balancer, replace `PROJECT_ID` and `ALB_NAME`:

```promql theme={null}
sum(rate(envoy_vhost_vcluster_upstream_rq{resourcemanager_datumapis_com_project_name="PROJECT_ID", gateway_name="ALB_NAME"}[5m]))
```

To add up several load balancers, select them with a regular expression, such as `gateway_name=~"alb-one|alb-two"`. To query these metrics in your own tools, [export them](/docs/operations/metrics-export.md).

### Access logs

To see the requests that reached your Connector, read the access logs of the load balancer that routes to it:

```bash theme={null}
datumctl alb logs ALB_NAME --since 1h
```

A `502` or `503` with nothing reaching your machine can mean the tunnel isn't connected. Check that the Connector is running on your machine. See [ALB access logs](/docs/alb/observability.md#access-logs).

## Follow the roadmap

> [card] [Connectors limitations and roadmap](/docs/connectors/limitations-and-roadmap.md)
>
> See what Connectors doesn't support yet and what Datum is building next.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.