Datadog & Observability Consulting
If your on-call team is drowning in alerts that don't mean anything, or you genuinely don't know whether your monitoring would catch a real outage, this is where I help. I work with Canada and US teams to audit and rebuild observability setups across Datadog, Grafana, and CloudWatch, so alerts map to real user impact instead of noise, and dashboards answer the questions people actually ask during an incident.
What's included
- Audit of existing Datadog, Grafana, and CloudWatch setups
- SLO/SLI design tied to real user-facing impact, not arbitrary thresholds
- Alert tuning to cut noise without losing real signal
- On-call and paging workflow review
- Documentation so your team can maintain and extend monitoring independently
- I bring alerts and operational workflows into Slack so on-call teams aren't context-switching between tools
Proof it works
- Deployed 60 production SLOs in 2 days using AI-assisted Terraform module refactoring.
- Built a Slack-based on-call paging system that eliminated 30 paid vendor seats.
- Reduced alert fatigue 80%.
Is this right for you?
This is a fit if your on-call rotation is getting paged constantly for things that turn out not to matter, or if you genuinely aren't confident your monitoring would catch a real outage before a customer does. It applies whether your stack is Datadog, Grafana, CloudWatch, or a mix of the three. The engagement is fixed-price and scoped up front, starting with a free 30-minute call to understand your current setup, what's paging people today, and what "good" would look like for your team. It's not a fit if you're starting from nothing and need a monitoring stack chosen and stood up from scratch with no existing tooling in place — that's a different, larger conversation worth having on the scoping call rather than assuming it fits this scope as described. Whatever's built or reconfigured — dashboards, alert rules, SLOs — is documented and handed over so your team can maintain and extend it without depending on me going forward. I reply within 24 hours and work with teams in Canada and the US.
FAQ
Do you work with our existing monitoring tools, or replace them?
The audit and optimization work is done on your existing stack — Datadog, Grafana, CloudWatch, or a mix — rather than ripping it out and starting over.
How long does a typical observability engagement take?
Typically a couple of days to a couple of weeks, depending on scope, complexity, and how quickly we get access and get oriented in your environment — the scoping call narrows this down before work starts.
Will this reduce how often our on-call team gets paged?
That's the goal of the alert-tuning and SLO/SLI work specifically — aligning alerts to real user-facing impact rather than arbitrary thresholds is what cuts noise — but the specific outcome depends on your current setup, which the audit establishes.
How it works
Simple, low-friction engagement. No lengthy contracts or discovery phases.
Tell me what you need
Fill out the contact form with a brief description of your challenge. I'll respond within 24 hours.
Quick scoping call
We jump on a 30-minute call to understand your environment, goals, and timeline. I'll follow up with a clear scope and fixed price — usually within a couple of days, up to a week for more complex asks.
I get to work
Hands-on delivery with regular updates. You get clean documentation and knowledge transfer — not a black box.
Done — and you own it
Everything I build is yours. I document it thoroughly so your team can maintain and extend it independently.
Ready to talk about observability & monitoring?
Tell me a bit about your challenge and I'll get back to you within 24 hours.
Get in touch →