Open standard
Instrument once and be able to change destination.
OpenTelemetry Engineering.
Design, deployment and governance of OpenTelemetry: collectors, pipelines, instrumentation and conventions.
The problem we solve.
OpenTelemetry is powerful, but its configuration grows fast: receivers, processors, exporters, different versions and conventions per team. Without governance, every collector ends up a special case.
What’s included.
- Design of collector pipelines
- Configuration of filtering, enrichment and sampling processors
- Application instrumentation
- Semantic conventions and common attributes
- Version management and configuration as code
How we work.
Five phases, always in the same order. Select each one to see what happens in it. In full projects they map onto the stages of our method.
We review what's monitored today, with which tools, which incidents went unnoticed and what it costs.
We design the collection layer with OpenTelemetry: agents, gateways, egress paths, common attributes and sampling.
We build the collector pipelines with their processors and leave the configuration version-controlled in your repository.
We check telemetry volume, latency and attributes at the pipeline output before deploying it across the whole environment.
We tune cardinality, sampling and detectors based on real usage to contain cost and noise.
Technical capabilities.
- OpenTelemetry Collector
- OTLP
- Processors: batch, memory_limiter, resourcedetection, filter, transform
- OTTL
- Tail sampling
- Semantic conventions
Use cases.
Uncontrolled collectors
Unify configurations and versions.
Data reduction
Filter and transform before sending.
Benefits for your organisation.
- Vendor independence
- Consistent, versioned configuration
- Cleaner data
- Contained transmission cost
Deliverables.
- Collector configurations
- Documented conventions
- Configuration repository
- Upgrade guide
Frequently asked questions.
Why OpenTelemetry?
It's the Cloud Native Computing Foundation's open standard for telemetry. You instrument once and choose the destination without touching the code.
Can we send to several destinations at once?
Yes, the collector can send the same signal to several destinations, useful during a migration.
Who maintains the collectors afterwards?
Your team, with versioned configuration and an upgrade guide. We can also do it for you as a managed service.
Shall we talk about OpenTelemetry Engineering?
Tell us about your situation. If this service is not what you need, we will tell you; if it is, we will propose a concrete first step.
Request this service