Monitor Manticore Search in Grafana with One Command

The most annoying kind of incident is when database doesn’t go down completely - it just gets slower. Users start noticing it right away. Complaints come in. Everything is technically still running, but clearly something is off. And that is usually the hardest part: not noticing the problem, but figuring out what is actually happening. When everything looks fine, but search is still slow Let’s take a pretty normal scenario. Search starts slowing down. It is not crashing. It is not returning obvious errors. The service is up. From the outside, nothing looks broken in a dramatic way. But users can feel it. So you open your monitoring: CPU looks fine. Average latency does not look too bad. No obvious alerts. At first glance, nothing really explains the slowdown. So you keep digging... You check the queue. Nothing jumps out immediately. You look at worker usage. They are busy, but not in a way that tells you much on its own. You check the logs. Still nothing obvious. And after a while you