For platform & SRE teams
Stop being the help deskfor every dashboard request.
Product teams get traces, logs and metrics without filing a ticket. You get the Kubernetes fleet next to their services, and incidents run in the same tool.
Every team on every cluster.
You deploy one Collector per cluster. Each team owns its SLO and gets its own pages, and you see the whole grid. Click a cell to see who gets woken up.
$ kubectl apply -k deploy/ferristrace-collector✓ 3 clusters · 13 namespaces
| team | prod-eu-1 | prod-us-1 | staging |
|---|---|---|---|
| checkout | |||
| payments | |||
| search | |||
| identity | |||
| ml-platform |
prod-eu-1 · ns/checkout
checkout
SLO: 99.9 % of requests under 400 ms
- pods
- 12
- deploys today
- 3
INC-212 · paged @checkout-oncall
Since the 14:02 sync it has burned error budget 6× faster than allowed. INC-212 paged the checkout on-call, so you can stay asleep.
Where the time goes today.
The steps it takes now, next to the steps it takes with FerrisTrace.
Today
4 steps · 4 tools- 1Jirareceive "add my service to monitoring"
- 2Prometheusadd scrape configs
- 3Grafanaclone a dashboard for them
- 4Slackexplain how to read it
With FerrisTrace
1 step · 1 tool- 1FerrisTracethe team creates its project and ingest key itself
Product teams serve themselves and you get back to the platform.
Start with these.
- InfrastructureYour Kubernetes cluster, next to the services it runs.Learn more
- Traces, logs & metricsFollow one request from the click to the database.Learn more
- Incident responseFrom the first alert to the postmortem, on one timeline.Learn more
- AI agentsAgents investigate with scoped FerrisKey tokens.Learn more
Give every team observability and keep your queue short.
Deploy it with our Kustomize manifests through ArgoCD, or try it on Cloud first.