Drops into your stack
A Tero distribution runs inside the collector, agent, or pipeline you already operate, or as a proxy in front. No new agents, no rip-and-replace.
Tero finds waste, risk, and noise in your telemetry estate, turns each fix into a reviewable policy, and helps the right team own, deploy, and improve it across the tools you already use.
A per-request trace from the router middleware is logging on every call to /v2/*. It ships at DEBUG, but the collector is keeping it, and nothing downstream reads it.
id: drop-api-gateway-middleware-tracename: Drop api-gateway middleware tracelog: match: - resource_attribute: ["service.name"] exact: api-gateway - log_field: LOG_FIELD_BODY contains: "requestContext entered" keep: none
Atomic, reviewable, reversible. Stops the bleed now; fix the code on your own schedule.
Exclusion filters sit behind admin settings.
Pipeline configs sit behind gatekeepers and deploys.
Tickets ask busy teams to clean up work they cannot see.
That is how platform teams become the bottleneck.
A telemetry policy is a small, reviewable control: what it matches, what it changes, where it runs, who owns it, and whether it is working.
Instead of one fragile pile of rules, every fix becomes something a team can review, own, deploy, and improve.
Built on an open standard, donated to OpenTelemetry as OTEP-4738 ->
Tero connects to the places your telemetry lives, builds a service-level model of events, volumes, owners, destinations, and risk, then runs standing checks for waste, noise, sensitive data, and policy opportunities.
A Tero distribution runs inside the collector, agent, or pipeline you already operate, or as a proxy in front. No new agents, no rip-and-replace.
Approved policies sync to the runtime automatically. Each runtime reports back hits, drops, and impact. No config rollout, no redeploy, no ticket.
The router compiles every policy into a single matching pass, built on Hyperscan, so p99 holds constant from 10 policies to 10,000. Orders of magnitude faster.
+ 14 more services
+ any conformant runtime
+ any OpenTelemetry sink
Some issues should be fixed in code. Some should stay as policies. Tero gives you immediate control, then routes the follow-up into the tools and agents your teams already use.
A debug log in the request path is shipping on every checkout call.
Less cleanup for platform. Clearer ownership for teams. Faster action when something goes wrong. Safer, cheaper, cleaner telemetry across the estate.
~40% less telemetry spend, on average
No more renewal sticker shock
A budget you can actually forecast
Stop paying to store data no one queries
Durable discipline, not one-time savings theater
Stop being the cost police
No more 2am fire drills from a runaway log
Stop chasing engineers to clean up after themselves
One place to see every policy: where it runs, what it saves
Stop being everyone's telemetry cleanup crew
Never be the one who blew up the bill
An honest mistake stops being an incident
No memorizing what's safe to log
Debug faster. Signal isn't buried in junk
No telemetry chores derailing your sprint
Built by the team behind Vector.dev · OpenTelemetry maintainers · telemetry policies are now an OpenTelemetry proposal