Benchmarking OpenTelemetry: Can AI trace your failed login?
1–10 of 85 posts
Re: Benchmarking OpenTelemetry: Can AI trace your failed login?
#2Re: Benchmarking OpenTelemetry: Can AI trace your failed login?
#3Even when it's not particularly effective, the additional information provided tends to be quite useful.
Re: Benchmarking OpenTelemetry: Can AI trace your failed login?
#4If everyone else is the problem... maybe you are the problem. To me this says more about OTel than AI.
My takeaway was more "maybe AI coding assistants today aren’t yet good at this specific, realistic engineering task"....
Re: Benchmarking OpenTelemetry: Can AI trace your failed login?
#5If everyone else is the problem... maybe you are the problem. To me this says more about OTel than AI.
Re: Benchmarking OpenTelemetry: Can AI trace your failed login?
#6I wouldn’t touch this with a pole if our MTTR was dependent on it being successful though.
Re: Benchmarking OpenTelemetry: Can AI trace your failed login?
#7Re: Benchmarking OpenTelemetry: Can AI trace your failed login?
#8Re: Benchmarking OpenTelemetry: Can AI trace your failed login?
#9Our humans struggle with them too. It’s the only domain where you need actually to know everything . I wouldn’t touch this with a pole if our MTTR was dependent on it being successful though.
MCP servers for monitoring tools are making our developers more competent at finding metrics and issues.
It'll get there but nobody is going to type "fix my incident" in production and have a nice time today outside of the most simple things that if they are possible to fix like this, could've been automated already anyway. But between writing a runbook and automating sometimes takes time so those use cases will grow.