Connect observability and CI tools
Bring live engineering signals into Vörr and map inconsistent service names across your toolchain.
Choose a connector
Open Connectors and select the tool you want to add. Supported categories include:
- Observability and metrics
- Error tracking
- Distributed tracing
- Logs
- CI/CD
Each connector card shows the fields and permissions required for that tool.
Create read-only access
Use the connector's instructions to create the appropriate token or service account. Prefer stable, least-privilege credentials.
For example, Jenkins REST access requires an API token even when SSO is used for the web interface, and Grafana should use a Viewer service-account token.
Test the connection
Enter the connection details and validate them. Correct the endpoint, authentication method or permissions if validation fails.
Map service names
The same service may have different names in Vörr, Datadog, Jenkins or another source. Use the service map to connect those names explicitly.
Vörr can attempt a name-based match, but the answer will identify it as inferred rather than explicit. Mapping important services is one of the most effective ways to improve answer quality.

Understand multi-source answers
When more than one connected source can answer a question, Vörr queries the relevant sources and reports their results separately.
It does not average conflicting values. Each result keeps its source and match quality, and one failing source does not erase successful results from the others.
Confirm the setup
Ask a source-specific question:
Is checkout erroring? Show me the last 15 minutes and identify the source of each result.
Confirm that the response uses the expected connector and service mapping.