What you runRunning OpenTelemetry?
You made the right collection bet. Now own the fleet.
OpenTelemetry is the one collection standard every vendor has to accept, and it carries no license. What it does not give you is a fleet: rollouts, health, drift, and knowing what actually runs where.
Free. No system access. No obligation. You keep the drawing.
Where the meter sits
OpenTelemetry carries no license. The meters sit at the destinations it feeds, and at the fleet consoles vendors rent back to you.
01Where OpenTelemetry stops short
Everyone offers you OpenTelemetry. Nobody gives you the fleet.
OpenTelemetry is the right collection standard, and every vendor will happily take what it sends. What is missing is the control plane: rollouts, health and drift across the fleet, run from your repository instead of a vendor’s console.
“Every vendor offers us OpenTelemetry, and nobody gives us a way to run it.”
LaterOpen collection is part of Phase 04, the footprint: first the pipeline in front of your SIEM, then AI triage on the clean data and remediation, then the fleet.
A fleet control plane you own. Rollouts, health and drift, from your repository.
- Why it happens
Every vendor now accepts OpenTelemetry and many ship their own distribution. None gives you a neutral way to run it: configuration rollout, health, version drift and knowing what runs where are left to scripts.
- What changes
Each collector runs under a small supervisor that dials out over OpAMP to a control plane in your account. Configuration rolls out in rings from your repository through CI/CD, a few hosts first, and the console shows every host, its health and whether it matches what was sent.
- How sure you can be
OpAMP is the OpenTelemetry standard for managing collectors. Nothing inbound opens to your network, and the repository is the state.
- How soon
Later, host group by host group, once the pipeline in front of your SIEM is proved.
- What it takes from you
Your diagrams and one call. We plan the order with you.
Your control plane
- A fleet plane you ownYoursConfiguration and rollout from a console in your account, under OpAMP.
- Ring deploymentsCI/CDTest hosts first, the estate after, from a pull request.
- Drift and healthWatchedEvery host, what it runs, and whether it matches.
- No per-agent licenseOpenNothing in the plane is rented back to you.
“We chose the open standard, and every host still runs a vendor’s agent beside it.”
LaterOpen collection is part of Phase 04, the footprint: first the pipeline in front of your SIEM, then AI triage on the clean data and remediation, then the fleet.
One collector, every destination. No vendor agent left on the host.
- Why it happens
Open collection was meant to end agent sprawl. Most estates still run a vendor agent beside the collector, for one feature someone depends on.
- What changes
The estate converges on one OpenTelemetry collector per host. Each vendor feature still needed is fed from it, and the agents retire host group by host group.
- How sure you can be
OpenTelemetry is the open standard the major APM vendors already accept. Nothing about your destinations has to change on day one.
- How soon
Later. We start with the logs in front of your SIEM, because that is where the money is. Open collection follows once that is proved, host group by host group.
- What it takes from you
Your diagrams and one call. We plan the order with you.
Your control plane
- OpenTelemetry collectorsOpenOne open collector on every host, built for your estate.
- A fleet plane you ownYoursConfiguration and rollout from a console in your account, under OpAMP.
- Changes as pull requestsAs codeAI native: an assistant drafts the change, your team reviews and merges it.
- No vendor agentsRemovedNothing on a host reports to someone else’s console.
- Monitoring, only what earns itYour callStep away from a vendor’s full architecture and keep only the features you value.
“Our collectors are open, and the only fleet console on offer is a vendor’s.”
LaterOpen collection is part of Phase 04, the footprint: first the pipeline in front of your SIEM, then AI triage on the clean data and remediation, then the fleet.
A fleet console you own, in your repository.
- Why it happens
Vendors sell fleet management over open collectors, and the pane of glass becomes the new lock-in.
- What changes
The fleet comes under OpAMP control from a plane in your account, with the console in your repository and no per-agent license. Changing a destination is a routing change, not a re-instrumentation project.
- How sure you can be
The detections, dashboards and alerts your team relies on keep firing where they do today. A move becomes a parallel run on the same routed feed, proven before anything is retired.
- How soon
Before your next renewal, if we start with the sources that drive it.
- What it takes from you
Your diagrams, your renewal date, and one call.
Your way out
- MigrationToday: Quarters of overlapping licensesWith you in control: Weeks: a parallel run, then a routing change
- Your dataToday: Their format, in their storeWith you in control: Open schemas, OCSF and OpenTelemetry, in your Lake
- HistoryToday: Stays behind when you leaveWith you in control: Replays into any tool you choose
- Collection and fleetToday: Their agents, their consoleWith you in control: A control layer and fleet plane you own
“We collect everything openly, and every destination still receives all of it.”
Send each destination what it is for. Keep everything else in your own Lake.
- Why it happens
Collectors export what they are configured to export, so the expensive platforms bill on everything the estate produces.
- What changes
A pipeline decides what each destination receives, so SIEMs and APMs bill on signal, and the full copy lands in storage you own.
- How sure you can be
Nothing is lost. The full copy stays in your Lake and replays on demand, and every routing rule is readable code. The reduction is measured on your own noisiest sources, before and after, in writing.
- How soon
With the first source. We start where the most volume sits, prove it, then continue.
- What it takes from you
Your diagrams and one call to start. We build it as code in your repositories and teach your team to run it.
What shrinks
- GB indexed by your SIEMOnly what detection reads is indexed. Duplicates, debug output and unread fields stay out.
- Tokens per AI investigationEvery query to the Lake returns only the fields the agent needs.
- Hosts on per-node licensesOrdinary hosts move to monitoring you own. The APM keeps the apps that earn it.
- Vendor licenses and modulesYou keep the features that earn their price, not the whole platform.
Shapes, not figures. Yours are measured on your own sources in the review.
02Today, and after
Today, and with the Blueprint
An estate already on OpenTelemetry owns its collection, but rollouts run by script, drift is found by accident, and every destination still receives everything.
Scroll the drawing sideways to see all of it.
What OpenTelemetry does best
OpenTelemetry won. It is the one collection standard every vendor has to accept, the collector reads practically everything a host produces with nothing changed in any application, and it carries no per-host or per-agent license. An estate that standardized on it owns its telemetry at the source, which is the position every other page on this site is trying to reach.
What it does not give you out of the box is a fleet. A collector is not the hard part. Running thousands of them is: configuration rollout, health, version drift, and knowing what is actually running where. That is the layer most estates are missing, and the one the platform vendors will happily rent back to you.
How it works, and where we sit
OpenTelemetry is the open collection standard every vendor has to accept: the Collector runs on every host as pipelines of receivers, processors, and exporters, reads metrics, logs, and traces with nothing changed in any application, and ships them anywhere over OTLP. It carries no license, and it has no alert engine of its own, so alerting lives as rules in the store you send metrics to. An estate already on it owns its collection, and the work is the fleet: OpAMP control from a plane in your account, a console in your repository, and then the Lake the collectors feed.
03The five verbs
What we keep, and what changes
Keep it and govern what flows in, shrink its footprint, cut what it costs, extend it with an agent, and replace only where replacement is honest.
- Keep
Your collectors and your instrumentation. Nothing about the collection bet changes, because it was the right one.
- Shrink
The per-vendor agents still lingering beside the collector on many hosts retire, and the estate converges on one collector.
- Cut
The control layer decides what each destination receives, so the expensive platforms bill on signal instead of on everything the collectors happen to produce across the estate.
- Extend
The fleet comes under OpAMP control from a plane in your account, with a console in your repository, and the Lake lands enriched history for the agent phases.
- Replace
The rented fleet consoles. The pane of glass over your collectors belongs in your repository, not in a vendor subscription, and it is the one thing on this page that was only ever rented.
The letters mark where each verb acts in the drawing with the Blueprint.
The fleet, controlled as code
Each collector runs under a small supervisor that dials out to a control plane in your account over OpAMP, so the fleet is managed from your repository with no inbound credential to your network.
Configuration changes roll out in rings from a repository your team reviews, a few test hosts first, the estate after. The console shows every host, its health, what it is running and whether that matched what was sent. It holds no state of its own to lose, because the repository is the state.
From there the Blueprint continues naturally: the control layer routes, the Lake accumulates enriched full-fidelity history, and the agents read it.
04The free architecture review
We draw your OpenTelemetry estate, free.
Telemetry engineers look at your whole environment and show you exactly where the cost, the waste and the hurdles are, and what your architecture could look like. No strings attached.
What you get
- Your OpenTelemetry architecture today, drawnEvery source, pipeline and destination, as it actually flows.
- The waste mapWhere you pay for data nobody reads, and what it costs you each year.
- Costs before and after, with estimatesWhat you spend now, and what the same coverage would cost.
- Your target architectureWhat your OpenTelemetry estate could look like, drawn on your own sources.
- Options for your business problemNot one product. The choices, with what each one costs and changes.
Who does it
A lead architect with 26 years in monitoring and observability, leading a team of senior engineers in telemetry engineering and pipeline design. The team that reviews it is the team that would build it.
What it takes from you
Your diagrams and one call. No system access.
What comes next
If it pays, a two-week proof of value on your noisiest source, free unless you go ahead. At least 20% less into your SIEM, every alert kept, proved on your data.
What it costs
Nothing
No strings attached. You keep the drawing, whatever you decide.
05Questions
What OpenTelemetry teams ask before they book
We run OpenTelemetry already. Why involve anyone?
Because collection and fleet are different problems. If your collectors are versioned, ring-deployed, health-visible, and centrally controlled from a repository, you have the fleet too and need nobody. If rollouts are scripts and drift is discovered by accident, the fleet layer is the missing piece.
Is the fleet plane another product we rent?
No. The supervisor and control plane speak OpAMP, the OpenTelemetry standard for managing collector fleets, and the plane runs in your account. The console is built for you and reads your repository. There is no per-node or per-agent license anywhere in it.
What about the destinations we send to?
They stay your choice, and that is the point. The control layer in front of them decides what each receives, so each platform bills on what it is actually good at, and changing a destination is a routing change rather than a re-instrumentation project.
Why is the review free?
Because the drawing is how you judge us. You see your own architecture, your waste and your options before you spend anything, and you keep the drawing whatever you decide. No system access, no obligation.
Are you a reseller for a vendor?
Yes, for certain vendors’ software. We are also the delivery partner and integrator on custom projects, directly or alongside your systems integrator. The pipeline subscription is in your name, bought from the vendor, its channel or through Logmetry where we resell it, and priced on its own line. We recommend what fits your business problem, even when that means changing nothing, and no SIEM or APM vendor pays us to recommend it.
What if the savings don’t hold on our data?
You see it measured before you commit. The two-week proof of value runs on your noisiest source, with success criteria signed before it starts, measured in your SIEM’s own license usage view. At least 20% less into your SIEM, every alert kept, proved on your data.
See your OpenTelemetry estate drawn, with the costs, before you spend anything
Run by a lead architect with 26 years in monitoring and observability. No system access, no charge, no obligation.
Free. No system access. No obligation. You keep the drawing.
What you get
- Your architecture today, drawn
- The waste map
- Costs before and after, with estimates
- Your target architecture
- Options for your business problem
What it costsNothing