Odigos
Get a demo
Odigos
The production context platform

Production context.For every decision.

Odigos records what runs inside every service, live, with nothing in your code. Your engineers, AI agents and security teams get the evidence they need.

Get a demo
metrics
traces
logs
traces
profile
function values
code "BLACK50"
rule nil
returned 0.00
checkout revenue is down 12%following a checkout that completedwhatever that path already recordsnothing here backing out, trying elsewheretrying the promo pathfinding out which functions randynamically instrumenting applyDiscount()
cause foundthe rule lookup came back empty

Running in production at

t-mobile
csaa
merck
avodaq
avetta
hp enterprise
inpost
deephealth
omnissa
The wait

Same incident, two AI agents. One opens a pull request. One answers.

The one that can only read what someone logged in advance adds a log line and waits for the bug to happen again. The one on Odigos asks production what the code did. Hours to days against seconds, on every incident, on every team.

without Odigosit opens a pull request
>why is checkout revenue down 12%
Traces look clean. 200s across POST /orders, p99 flat. The only thing I cannot see into is the discount path.
Read(promo.go)Read 84 lines
applyDiscount returns early when the rule lookup misses, and nothing logs what it returned. I cannot confirm this from here.
Update(promo.go)Updated promo.go with 1 addition
41 rule := rules.For(code)
42 if rule == nil {
43+ log.Info("discount", "returned", 0.0)44 return 0
Opened PR #4471. Once it is reviewed and deployed I will know after the next occurrence.
hours to days before it can answer
with Odigosit queries production
>why is checkout revenue down 12%
Traces look clean. 200s across POST /orders, p99 flat. The only thing I cannot see into is the discount path.
odigos - find_functions("checkout", "discount")84 functions, applyDiscount at promo.go:41
odigos - capture("applyDiscount", args, returns)attached in 1.2s, nothing redeployed
odigos - read("applyDiscount")code "BLACK50", cart 49.00, returned 0.00
Found it. BLACK50 is missing from the rules table, so applyDiscount returns 0 and every order using it paid full price.
seconds and it can ask the next one
The technology

Inside every service. From outside the code.

Odigos DeepBPF is an eBPF runtime built from scratch to see inside the application, not just the kernel. The functions that ran, the values they carried, as it happens. Under 1% CPU. Nothing loads into your process.

everyone else stops herethe syscall
POST /orders214ms · 200 OK
GET /cart31ms · 200 OK
that is the whole story they can tell
the edge of your service
odigos reads hereinside the code
applyDiscount("BLACK50", $49.00)
returned $0.00on every call
the value that explains the drop, out of a running service

Every service on day one

Every language, every version, every binary. Even the ones nobody owns. One command.

AI agent
investigating
Production
342 services
asks ❯ capture goroutine stack for checkout
stack + 14 spans returnedin policy

Odigos Autofocus

Captures deeper where a service drifts, inside the scope your policy sets.

POST /checkout402ms
↳ auth.verify38ms
↳ cart.load64ms
↳ pg.query orders274ms
↳ cache.set4ms
pg.query orders · missing index · +274ms

Feeds what you already run

Exports OpenTelemetry into Datadog, Grafana, Splunk or your SIEM. Deeper data, same dashboards, no migration.

One record, three readers

Debug it. Defend it. Check what you shipped.

The same record answers an engineer after a page, a security policy on every call, and a coding agent after every deploy.

Why did checkout fail, and what changed?
BLACK50 missing from the rules table since 02:58. 312 orders paid full price.
01 / Observability

Root cause, not a guess.

Where the trace ends, ask the service what its code did.

Observability
Which of ten thousand permitted calls should be refused?
One reflective call in the ticket service. Named by policy. Refused.
02 / Security

Block the call. Keep the service.

Your policy names the function. The call fails there. No redeploy.

Security
Did the retry change I shipped at 14:30 do what I meant?
No. Every failed payment now retries against the slow region. Revert one flag.
03 / Coding agents

Wrote it at 14:30. Checked it at 14:31.

Claude Code, Cursor and Copilot check what their change did on real requests.

Coding agents
14-day trial

Ask production. Get the answer.

Get a demo

One command. Every service. Nothing in your code.

From the team

Latest from the blog.

All posts