Drops into your stack
A Tero distribution runs inside the collector, agent, or pipeline you already operate, or as a proxy in front. You install nothing new and replace nothing.
From the creators of Vector.dev
Make teams own the telemetry they send.
Tero finds bad telemetry, shows who owns it, and turns the fix into a policy your teams can ship.
Works with Datadog, Splunk, OpenTelemetry, and the telemetry stack you already run.
Your telemetry scaled.
Your controls still run through you.
More AI agents
More code
More features
More deploys
More services
More telemetry
Manual controls
cost dashboardssampling rulesexclusion filterspipelinestiered storage
A 10x bill spike
Your day, derailed
Renewal shock
Chasing engineers
The cost police
Secrets in logs
Today, telemetry problems become platform work.
Add an exclusion filter. Edit the collector config. File a ticket. Ping the team. Follow up again. Explain the spike. Repeat it next week.
The team that caused it never owns it.
Tero finds bad telemetry and the team that owns it.
Tero watches your logs, detects cost and compliance issues, and shows the service, team, impact, and affected events behind each one.
Policy Control
Every telemetry issue becomes a policy.
A policy is the fix: small, reviewable, scoped, auditable, reversible, and vendor-neutral. It is open YAML your team owns, not vendor state. Not a dashboard note. Not a buried ticket. Not another hand-written exclusion filter.
Six properties · no exceptions
01
File-backedopen YAML you can inspect and version
02
Atomicone issue, one policy, one owner
03
Scopedtarget a service, event, route, or attribute
04
Reviewableapprove the change before it ships
05
Portableruns across the telemetry tools you already use
06
Reversibleroll back without changing app code
Built on an open standard, donated to OpenTelemetry as OTEP-4738 ->
Policies run upstream.
Deploy policies into OpenTelemetry Collector, Vector, Tero Edge, or the pipeline you already run. Drop, sample, redact, or route telemetry before it hits storage, indexing, egress, and vendor bills.
Clean signal
host · ip-10-0-12-44 · us-east-1
Policies sync to the runtime
Approved policies sync to the runtime. Each runtime reports back hits, drops, and impact. You skip the config rollout, the redeploy, and the ticket.
10,000 policies, one pass
The router compiles every policy into a single matching pass, built on Hyperscan, so p99 holds constant from 10 policies to 10,000.
Teams review and ship their own policies.
Platform keeps the guardrails. Tero finds the issue, the owning team reviews the policy, the policy ships through your workflow, and Tero verifies the result.
Your teams
run the workflow themselves@platform@checkout@payments@commerce
Tero control plane
Tero finds an issue and shows the team that owns it. You are no longer the handoff point for every fix.
Your teams
each reviews and ships its own policiesTero control plane
liveYour infrastructure
Your services
api-gatewayx8
checkoutx4
paymentsx3
+ 14 more services
Data plane
OTel Collectorcollector
Vectordrop-in
Tero Edgezig · 6mb
+ any conformant runtime
Destinations
Datadogissue found
Splunk
CloudWatch
+ any OpenTelemetry sink
Resolution
Policies fit the way your teams already work.
A policy stops the damage now. Ownership stays with the team. If the code fix ships later, Tero sees the policy go inactive and tells you when it is safe to remove.
ISS-1247HOT PATH · COSThigh
Debug logging exploded in the checkout hot path
A debug log in the request path is shipping on every checkout call.
- Projected cost
- +$25K/yr
- Records
- 45M/day
- Owner
- @platform
LifecycleStop damage, then retire
- Deploy policy
- Open Jira
- Hand to Claude Code
- Retire policy
Finally, telemetry that works for everyone.
Leadership gets fewer surprises. Platform gets out of the cleanup loop. Engineering teams own the data they create.
Spend and risk stop becoming surprises
Fewer renewal shocks to explain
A telemetry budget you can forecast
Less sensitive data landing downstream
Spending discipline that holds quarter over quarter
Get out of the cleanup loop
No more 2am fire drills from a runaway log
Stop chasing teams to clean up after themselves
One place to see every policy: where it runs, what it saves
Keep control without owning every fix
Own the telemetry your services create
See the context behind every requested fix
An honest mistake stops being an incident
Debug faster. Signal is not buried in junk
Fewer random cleanup pings derailing your sprint
Built by the team behind Vector.dev · OpenTelemetry maintainers · telemetry policies are now an OpenTelemetry proposal