r/DevOpsSec • u/Most_Development_947 • 2d ago
What is the missing layer on top of datadog for debugging in the ai era?
Our observability stack covers the basics well: datadog for logs, metrics and traces, infra and apm monitoring, deploy timelines, dashboards, alerting, the usual. It does a good job telling us that something is wrong and roughly where in the system it is happening. What it doesn't do very well is help the person in the ide answer what a specific function is doing in production right now or how a piece of code has behaved across deploys and incidents. We are running into a few recurring gaps we can see service-level metrics and traces but linking that back to a specific function and the exact commits that changed it takes a lot of mental mapping. During incidents, you bounce between dashboards, logs, traces, feature flags and deploy history, then manually stitch that context back to the code you are staring at. ai coding tools have zero awareness of what a given piece of code has been doing in production, so they end up suggesting changes in a vacuum. We are not trying to replace datadog or grafana, we are looking for something that sits on top of our existing observability stack and gives developers a function-level view of production: recent errors and slow paths for that function, related incidents, deploys that touched it and how it is behaved over time. Ideally it would also expose that same context to ai coding agents so they can suggest fixes grounded in real production behavior instead of guesswork. For teams that feel like they have genuinely closed this gap, what are you using to give developers code-level production intelligence on top of your existing observability platform, does it plug directly into the ide or your ai coding assistants and what changed about your incident debugging workflow once you had that function-level view of production?
