Skip to main content
Every data source has a detail page in your telemetry settings that shows how it’s doing: its connection health, its query results, and why queries failed. This page covers what you’ll see there and how to fix each problem.

​
Connection health

Each data source carries a connection status from its most recent check:
  • Connected: the last check passed. Nothing to do.
  • Degraded: the source is usable and Nexus keeps querying it, but something non-blocking is off, most commonly that the source holds no recent data. Check the detail on the data source’s page to see what.
  • Connection failed: the last check found a blocking problem, so the source can’t currently be reached or used. Run the connection test to see which requirement failed.

​
When a data source needs reconnecting

When a data source stops being usable, its page shows a banner and Nexus pauses queries against it until you act. This happens for three reasons:
  • Authentication failures: the provider repeatedly rejected the credentials, so Nexus stopped querying the source and flagged it. Reconnect with fresh credentials to restore access.
  • Missing permissions: the credentials still authenticate, but a permission Nexus needs has been revoked. Grant the missing permission to the existing credential; reconnecting with the same key changes nothing.
  • Configuration required: the source is missing something it was never given, such as a database discovered through a provider that has no credentials yet, or a private resource Nexus can’t reach without a proxy. Finish the setup from the data source’s page.

​
Testing the connection

Select Test connection on a data source’s page to run a fresh check. It works through each requirement in turn: reaching the endpoint, authenticating, permissions, access to the data. When one fails, it names exactly what’s missing and how to fix it, down to the specific permission to grant.

​
Failed queries

The detail page also breaks failed queries down by category, so when a source has a low query success rate you can see why. Most categories are about the data source itself; a couple are things you can fix directly.
A healthy source occasionally errors, that’s normal. It’s a sustained shift in one category that’s worth acting on, like a jump in Unauthorized (reconnect) or Rate limited (provider limits).

​
Queries succeed but return nothing

The detail page separates queries that returned data from ones that came back empty, so a source that always returns nothing stands out even when every query succeeds. The common causes:
  • The connection is scoped to the wrong place: an index pattern, dataset, or project that doesn’t hold the data your team asks about. Check the data source’s configuration.
  • The data has aged out: queries target a window the source no longer holds. Check the retention settings below.
  • The source genuinely doesn’t hold that data: enable the sources your responders reach for during incidents instead.

​
Retention windows

Nexus queries within a data source’s retention window, and a query whose time range falls outside it fails as an invalid query. Nexus learns retention where the data source reports it, and you can set it yourself under Data source retention in the data source’s settings. If a source’s retention has changed (say you shortened it to cut costs), update it there so Nexus stops reaching for data that’s gone.

Telemetry overview

What you can connect, and how providers and capabilities fit together.

How telemetry works

Routing, query planning, guidance, and memory.