Observability

Logs, metrics and traces that tell you what’s wrong before customers do.

Talk to an engineer
Problems we solve
“We find out about outages from customers.”
“There are dashboards, but nobody looks at them.”
“Alerts fire all night and mean nothing.”

What we do

Advise

Observability consultancy

An assessment of your Observability setup, with findings ranked by risk and effort.

Build

Observability delivery

We design and build it with your team, in your accounts, documented as we go.

Run

Observability support

Monitoring, patching and upgrades, with incident response agreed per contract.

Teach

Observability training

Workshops and pairing on Observability, built around your own systems.

Tools we work with

Platforms

  • New Relic
  • Datadog
  • Grafana Cloud
  • Elastic

Open source

  • Prometheus
  • Grafana
  • Loki
  • Tempo
  • Mimir
  • Thanos
  • Jaeger

Instrumentation

  • OpenTelemetry
  • Fluent Bit
  • Vector

Cloud-native

  • CloudWatch
  • Azure Monitor
  • Application Insights
  • Cloud Monitoring

Errors & uptime

  • Sentry
  • Better Stack
  • Checkly

How an engagement runs

  1. 1 A call. 30 minutes with an engineer to understand the problem.
  2. 2 A look. Read-only access or a walkthrough, so we scope from facts.
  3. 3 A proposal. Scope, deliverables and a price model: fixed scope, day rate or retainer.
  4. 4 The work. In your accounts and repositories, alongside your team.
  5. 5 A handover. Documentation and a session with your team, so you’re not dependent on us.

Proof

A recent Observability engagement. We keep client names private, but the problem, the work and the outcome are exactly as they happened.

See our work
Case study · anonymised
UK marketplace scale-up
Challenge
We find out about outages from customers. That was how the client put it on the first call.
Approach
We agreed what “healthy” means for each service, instrumented logs, metrics and traces to match, and rebuilt alerting around it.
Stack
OpenTelemetry · Prometheus · Grafana · Loki
Result
The team hears about problems from its alerts, not its customers, and the overnight noise has gone.

Questions

Do you work in our accounts or yours?

Yours. Everything we build lives in your cloud accounts and repositories from day one, so there is nothing to migrate when we finish.

Can you work alongside our own team?

Yes, and we prefer it. We can run a project ourselves, embed engineers in your team, or pair with your people so they pick it up as we go.

How is this priced?

Depending on the work: a fixed-scope price, a day rate or a monthly retainer. We agree it in a written proposal before anything starts.

Tell us what’s broken, slow or expensive.