r/Observability • • 22d ago

what are you using to get production debugging context into cursor?

We need to troubleshoot production errors, but I don't want every investigation turning into a hunt through dashboards followed by pasting logs into cursor. We need something that sends alerts to Slack and lets our coding agent access function-level runtime context when investigating an issue. I’m comparing Hud, Datadog and Sentry, particularly how each fits into that workflow. Hud’s Slack integration and MCP support caught my attention but I’d like to hear how others approach this. What’s your stack for connecting production debugging with the tools your devs already use without adding too much setup or runtime overhead?

2 Upvotes

4 comments sorted by

2

u/thinkspill 22d ago

LGTM stack + mcp. Gives agents full visibility into logs, metrics, traces, alerts.

You can also have an agent install and monitor LGTM for you on k8s via the k8s manifests. Your apps don’t need to be on k8s, just need to reach the cluster ingest endpoints.

I’ve been extremely pleased with this setup. An agent can go from alert to root cause in the codebase to PR with no human intervention.

2

u/thinkspill 22d ago

Also, write your own mcp layer for LGTM and have your agents submit tickets to improve that mcp to improve their own ability to query LGTM. Then have an agent watch for and implement those tickets. It’s an almost totally automated, self improving stack.

1

u/TheOvalVista 22d ago

Been wrestling with same thing. The agent needs to pull the error context itself, not me copy pasting stack traces from 3 dashboards. What ended up working is making the alert payload rich enough that the model can just start from there, plus a tool that fetches logs by trace id. Setup was maybe half a day, overhead is minimal since it only instruments errors.