OpenTelemetry consulting
We set up OpenTelemetry with your team: your services instrumented, the OpenTelemetry Collector in place, and traces, metrics and logs sent to the tools you choose.
Email usGuides on this topic
What we deliver, part by part
From your code to your tools.
Instrumentation plan
Which services, which signals, and where zero-code instrumentation is enough.
Zero-code instrumentation
Agents and libraries that instrument a service without code changes. On Kubernetes, the OpenTelemetry Operator can add them to your workloads.
Code-based instrumentation
Spans and metrics for the steps that matter to your business, added in the code with your team.
The Collector
The OpenTelemetry Collector receives, processes and exports the data, so you do not run a separate agent for each tool.
Names and attributes
One naming scheme across all services, based on the OpenTelemetry semantic conventions, so data from different services lines up.
Filtering and sampling
What is kept, dropped or sampled, decided on purpose. Traces sampled when they start, or in the Collector after the trace is seen.
Moving off vendor agents
Service by service, with the old and the new data compared before the old agent is removed.
Typical situations
-
Each tool needs its own agent, and changing tools means changing every service.
-
Your .NET applications use the Application Insights Classic API SDK 2.x.
Microsoft retires the .NET Application Insights Classic API SDK 2.x on 31 March 2027. Microsoft Learn
-
A trace stops at the edge of a service, so a request cannot be followed from start to end.
-
OpenTelemetry is in place, but each service names its data differently.
-
Telemetry volume grows, and nothing filters or samples it before it is stored.
What you get
- A written instrumentation plan, service by service.
- Services instrumented with OpenTelemetry, with your team.
- The Collector configuration as code, in your repository, with the filtering and sampling rules written down.
- A naming guide your teams can follow.
- A runbook for running and upgrading the Collector.
How it starts
Review, plan, build.
-
Review
We look at your services, agents, telemetry and tools.
YOU RECEIVEA written review: what is instrumented today, what is missing and what it costs.
-
Plan
Which services first, zero-code or code-based, the Collector setup and sampling.
YOU RECEIVEA written plan, service by service, with effort.
-
Build
We instrument the services and set up the Collector with your team.
YOU RECEIVEServices sending data through the Collector, documented.