Connect signals
Signals are the production and deploy data production monitoring reads: errors, analytics, session replay, observability, and deployments. Connect them so production monitoring has production to look at, not just your code.
Why connect signals
With a provider connected, production monitoring proposes work backed by what it finds there: an error that started after a deploy, a usage drop, a failing check. With nothing connected, it plans from the repository alone.
Connecting a provider does not change what production monitoring is allowed to do. It adds one more source of evidence it can read.
Providers you can connect
Seven providers connect:
- Sentry for error tracking.
- PostHog for product analytics.
- Honeycomb for observability.
- Datadog for infrastructure, logs, and APM.
- Vercel for hosting and deployments.
- LangWatch for LLM tracing.
- FullStory for session replay.
- and more
Each connects read-only. Sentry connects through OAuth; Honeycomb connects with a configuration key. The others connect from their own settings card.
Providers Coldtea recognizes but does not connect yet
Reading your repository, Coldtea can recognize dozens more providers than the seven above, across error tracking, analytics, alerting, uptime, and logging. Recognizing a provider is not the same as connecting to it. Those extra providers are planned, not working: Coldtea can tell you it saw one in the code, but it cannot read from it yet.
When that happens, Coldtea surfaces it as a request rather than a live connection.
How connecting works
The connection flow lives behind the Monitoring screen. Connecting a provider follows the same shape:
- Open the provider you want to connect.
- Complete its authorization: an OAuth handoff for providers that support it, or pasting a read-only key for the ones that use a key.
- Return to Coldtea and wait for the connection to show as connected.
Coldtea also surfaces providers it detected in your codebase, so the ones you actually use are easy to find rather than buried in a long list.
After connecting
Once a provider is connected, production monitoring reads it on the next daily run, and what it finds shows up as tasks with the source signals attached. Connect a provider before a run if you want that run to see it.
For the provider list and how these connections feed production monitoring, see observability integrations.