Telemetry

Telemetry is the hard signal that explains what your system was actually doing: error spikes, latency changes, log lines, and the dashboards your team already trusts. Connect the observability tools your responders reach for during an incident, and Nexus can query them directly. It learns the shape of each source, including the queries in your own dashboards. So it queries them the way an engineer who knows your systems would, not with generic guesses. Once you’re connected, Nexus uses your telemetry in two places:

• During an investigation: Nexus queries your sources to confirm or rule out a hypothesis. It’s the evidence that carries the most weight, and verifying against live system state is what gives an investigation the most conviction in a finding.
• In the agent: ask the agent what your systems are doing, from Slack, the dashboard, or the mobile app. It queries the same sources to answer, whether or not there’s an incident open.

​

What you can connect

Connect a provider to bring several data sources at once, or connect a data source directly. Providers Connect directly Connecting an HTTP API or an MCP server works differently: those are connectors, which give an investigation tools beyond telemetry.

​

How telemetry is modeled

Some tools host others. Connect Grafana once, and Nexus can discover the data sources behind it: Loki for logs, Prometheus for metrics, Tempo for traces, and more. AWS works the same way: it exposes accounts and regions, then CloudWatch, EKS clusters, OpenSearch domains, and RDS databases. So does Google Cloud, which exposes projects, and the GKE clusters running in them. You connect the provider once, then choose which of the discovered data sources to enable. The Grafana stack is connected this way only: there’s no separate Loki, Prometheus, Tempo, or Pyroscope entry in the connect flow. Connect Grafana, and they come with it, using Grafana’s own credentials. Other tools are connected directly and stand on their own. Some data sources work either way: a PostgreSQL database or a Kubernetes cluster can be connected directly or discovered behind a provider.

​

Capabilities

Each data source provides one or more capabilities, which is what Nexus uses it for:

​

Enabling data sources

Each data source can be enabled or disabled, which controls whether Nexus can use it. Which state it starts in depends on how the data source arrived:

• Data sources discovered through a provider start disabled, so you opt in deliberately.
• Data sources you connect directly start enabled.

Either way, you can turn each one on or off from your telemetry settings. Review the list after connecting a provider and enable the sources your team uses.

​

Learning your stack

Nexus doesn’t query blindly. For each connected data source we continually learn how to query it well in your environment. We discover its real labels and fields, learn the query patterns in your own dashboards, and remember what worked in past investigations. That’s what lets a query filter on the attributes you actually use and reach for sensible defaults, instead of guessing against an unfamiliar stack. Routing a question to the right data source, translating it into the right query language, and the guidance and memory the system builds over time all sit behind this. See How telemetry works for the full picture.

​

FAQs

​

Related