Overview
Point it at a repository and it injects the OpenTelemetry SDK, branches, and opens a ready-to-merge pull request. Multi-stack, not one reference language.
Key features
- OpenTelemetry SDK injected on a dedicated branch
- Multi-stack, not one reference language
- Nothing reaches main without a human approving the diff
- Spans arrive carrying the shared correlation key
How it works
- Step 1
Point at a repository
Give it an HTTPS repo URL, the source branch, and a token with repo scope. Optionally name the service.
- Step 2
The SDK gets injected
OpenTelemetry tracing and metrics instrumentation is written into the codebase on a dedicated branch — multi-stack, not one reference language.
- Step 3
Review a pull request
You get a ready-to-merge PR. Nothing reaches your main branch without a human approving the diff.
- Step 4
Telemetry arrives correlated
Merge, and spans land carrying the shared correlation key — so the service map draws itself and logs link to traces immediately.
Delivery
One-click Instrumentation is part of the full platform in both delivery models — there is no cut-down edition.
SaaS · Fully managed
We run the platform, handle upgrades, scaling and backups. You point your collectors at an endpoint and start asking questions the same afternoon.
PaaS · Your infrastructure, our platform
The full platform deployed into your own Kubernetes clusters or VMs, with telemetry never leaving your network boundary. We operate and support it where you host it.