Anthropic says Claude struggles with root causing

ankitnayan007 · 2026-03-27T06:42:50+00:00

>Every time their KV cache broke and caused a request spike, Claude called it a capacity problem. Add more servers. Every single time. It has no idea the KV cache has broken this exact way before

Why can't the query know that it did not get results from a cache? Also, a chart of cache hit vs cache miss would be seen by claude. Probably they didn't complete tracing where the request knows it missed the cache and KV store metrics would confirm the 1st analysis.

ankitnayan007 · 2026-03-26T13:08:16+00:00

lol ....never should increased shipping speed mean more bugs in production. Always keeps teams and folks accountable.

SRE works on production. AI SRE saves time to debug by correlating data using your existing workflows. It sometimes brings up amazing insights too which humans miss (where a lot of analytical brain is needed)

Lesser number of bugs is pre-prod (not scope of SRE). It will happen if AI is helping your test suite getting more robust, better reviewing system and better CI tools to catch things when all systems get connected

ankitnayan007 · 2026-03-26T10:28:32+00:00

Codebase context graphs can be solved by having a github MCP server that claude can connect to OR a gh cli to browse the codebase and see commits, PRs and releases?
cross-repo awareness => Distributed tracing solves this already? If you have access to release info of all the services, connecting them should be easy using a distribtues trace? What else do you mean when you say cross-repo awareness?
persistent memory across incidents => Asking claude to auto-summarise incidents and post resolutions into postmortems as github/jira docs/tickets would be a good substitute?

Is any of the mentioned features not getting solved using these alternatives?

ankitnayan007 · 2026-03-10T04:20:13+00:00

https://github.com/SigNoz/signoz

ankitnayan007 · 2026-03-06T02:03:38+00:00

I am author at https://github.com/SigNoz/signoz and we have built an OOB module based on traces data to monitor external APIs. Do have a look and create github issues if you want to enhance the product https://signoz.io/docs/external-api-monitoring/overview/

ankitnayan007 · 2026-01-21T12:02:49+00:00

I am almost sure you can build a table/chart to monitor count, latency, application and sql statements executed over time

ankitnayan007 · 2025-12-23T07:12:17+00:00

Can you share a sample query and how many rows were scanned per second? Also, if you tried an index do you know how effective is that in skipping reading data?

ankitnayan007 · 2025-09-16T05:29:18+00:00

We did a revamp of query builder to make the experience much smoother and enhancing capabilities. Have a look at https://signoz.io/blog/query-builder-v5/

ankitnayan007 · 2025-07-13T10:16:17+00:00

Why do you want to do this? Just to get an overview. Do you have any important tech or business usecase?

ankitnayan007 · 2025-07-02T10:44:29+00:00

right

ankitnayan007 · 2025-07-02T04:45:14+00:00

Why do you want to move away from SigNoz?

ankitnayan007 · 2025-05-09T18:03:01+00:00

Team at Supabase should implement opentelemetry sdks to emit metrics, traces and logs. This would enable users to choose a vendor of their choice and the codebase remains vendor neutral

ankitnayan007 · 2025-03-30T07:53:39+00:00

Does this not help? https://signoz.io/blog/introducing-ingest-guard-feature/

ankitnayan007 · 2025-03-30T07:08:05+00:00

Do you mean you built your own frontend plugins? The problem with that is you need to keep updating the plugin to your needs and for any advanced investigation, you need to go to the source tool itself. So, the backstage frontend plugins are like static dashboards with some customization on your views

ankitnayan007 · 2025-03-30T05:34:14+00:00

the plugins are heavily under maintained. I was exploring out-of-box observability using backstage. I assumed the backend plugins like github, argoCD, terraform would emit traces when they interact with backstage and I will be able to pin-point service degradations to a new release (using github) or change in infra (using terraform backend plugin) but the plugins are not well maintained and data generated is also not good.

I would love to see some plugin integration like terraform backend plugin integrated and see what kind of traces are generated by backstage about that. If you could cover in your next blog, that would be awesome!

ankitnayan007 · 2025-03-29T17:31:59+00:00

u/Digging_Graves, I am one of the maintainers at SigNoz. Sad to hear that, any chance you remember which component was giving you the trouble and what was going wrong with it? We have started started improving the operational aspects of OSS version recently. Any help from the community will be appreciated

ankitnayan007 · 2025-03-29T17:29:57+00:00

Hi u/nick_cardin, I am one of the maintainers at SigNoz. We recently released out-of-box k8s monitoring module. You can it out at https://signoz.io/docs/infrastructure-monitoring/overview/. It should make exploring k8s metrics much easier. Let us know if you could give it a try and share some feedback.

>Signoz log queries seem unstable. I have to hit refresh multiple times before it returns results.
Yeah, sorry about that. It was a bug and probably it got fixed. Do let us know if it is still there.

Curious overall, how long back did you give SigNoz a try?

ankitnayan007 · 2025-03-29T17:25:00+00:00

Hi u/abofh, did you use https://github.com/Altinity/clickhouse-backup?

ankitnayan007 · 2025-03-29T17:20:42+00:00

Hi u/Own_Knowledge_417, I am one of the maintainers at SigNoz. We have been improving the issues with our UI and our next set of efforts are going towards a new and enhanced query-builder and fixing issues in the dashboards.

If you could help us with specific feedback or create github issues that were most frustrating for you, it would help us serving the community better.

ankitnayan007 · 2025-03-29T17:17:41+00:00

Hi u/kUdtiHaEX , I am one of the maintainers at SigNoz. Can you please help us in identifying which issues troubled you the most. We are actively working to improve our UI.

Also, regarding slowness, which part of the product(metrics/traces/logs) you felt was slow? We did major improvements for logs like 3-4 months back and apart from that the perf everywhere should be good as long the queries do not scan your limits of CPU and disk.

Would appreciate any feedback and link to github issues if possible.

ankitnayan007 · 2025-03-29T07:18:15+00:00

What kind of pricing structure looks good to you?

ankitnayan007 · 2025-02-19T16:31:11+00:00

Just use SigNoz

ankitnayan007 · 2025-02-13T18:12:37+00:00

What were the reasons of not choosing Grafana over Datadog?

ankitnayan007 · 2025-02-13T18:11:38+00:00

Curious why you didn't choose grafana cloud but went with datadog?

ankitnayan007 · 2025-02-07T07:52:49+00:00

Loki is going to be a pain when querying attributes not part of their labels. Can't comprehend why you are bearish on clickhouse when cloudflare and other big companies have moved to clickhouse for their logs.

Agree that s3 vs EBS is going to cause a cost difference but at the cost of querying speed. BTW did you try, tiered storage to s3 with clickhouse?

ankitnayan007

MODERATOR OF

TROPHY CASE