ApivomApivom
Get Demo

Apivom Odin — error tracking that tells us before you have to

Odin is the error tracking and tracing layer behind the Apivom products. Errors and slow requests from web and server apps are grouped into issues, with readable stack traces, so engineers can triage production problems early. Odin is included with the products and is not sold separately.

Infrastructure layer

Odin in numbers

90days
Days of event retention
3
Newest releases keep their source maps
10min
Minutes between ingestion canary checks

Production problems, found and explained

Every Apivom app reports to one place, so a failure is grouped, tied to a release and traceable to the line that caused it.

Errors grouped into issues

Repeated errors are grouped into one issue instead of a flood of events, so engineers see what is broken and how often.

Performance traces

Slow requests are traced across the app, with sample rates that can be tuned per app, so a slowdown has a place to start looking.

Readable stack traces

Each build is tagged with its release, and source maps are uploaded for it, so a browser error points at real code, not minified output.

A fixed retention window

Events are kept for 90 days, long enough to compare a problem with what came before it.

An ingestion canary

A check runs every 10 minutes to prove events are still arriving, and the stack heals itself when they are not.

Alerts by email

Issue alerts go out through the platform mail service, so the right people hear about a new problem without watching a screen.

Included with the products

How the Apivom products use Odin

You do not set Odin up on its own. The Apivom apps send their errors and traces to it, and Apivom engineers use it to follow production. Here is what reports to it today.

  • Web apps. Iris, Pivot, Abu, Orbit, Mars, Atlas, the admin console and the Apivom websites all report browser and server errors.
  • Server services. The Atlas gateway, Vesta and the Staff workers report errors and traces from the server side.
  • Python services. The Abu engine and the Halo agent and background services report through the Python SDK.
  • Halo’s web interface. Halo’s web UI sends a minimal report, so a failure in the browser is still seen.
For Apivom engineers

Triage before customers notice

Odin is where Apivom engineers look first when something in production misbehaves. It is built to be trusted: if events stop arriving, that is itself caught.

  • An issues console. View, filter, bulk resolve, ignore and reopen issues from the Apivom admin console.
  • Sign-in through Key. Organisation sign-in goes through Key, the Apivom identity layer, so there are no separate accounts.
  • A pipeline that watches itself. The ingestion canary and alert rules in Otto flag broken ingestion instead of leaving silence.

Frequently asked questions

What is Apivom Odin?

Odin is error tracking and tracing. It collects errors and performance traces from every Apivom app, groups them into issues, keeps release tags and source maps so stack traces are readable, and is where Apivom engineers triage production problems.

Is Odin sold separately?

No. Odin is an infrastructure layer that is included with the Apivom products. You do not buy or set it up on its own. If you want to know how it supports your use of Iris, Mars or the other products, talk to us.

What data does Odin collect?

Errors and performance traces from Apivom web and server apps. In apps where user context is enabled, an event carries the signed-in user, roles and active organisation. Cookies, authorization headers and request bodies are not collected.

How long are events kept?

Event data is kept for 90 days. That gives engineers a window to compare a new problem with earlier ones. Source maps are kept for the newest 3 releases of each project, so storage stays bounded.

How do releases map to errors?

Each deploy build is tagged with the git commit it was built from, and its source maps are uploaded during that build. An error is then tied to a release and shows the original code instead of minified output. The source maps are not shipped with the app.

Can customers use Odin directly?

Odin is the tool Apivom engineers use to follow production, and they sign in through Key. Customer-facing dashboards or status pages are not part of what Odin offers today. If you need visibility into an issue you hit, talk to us.

Production problems should not be a surprise

Odin comes with the Apivom products. Talk to us about how Apivom keeps an eye on what runs in production.