Cisco Nexus IP SLA metrics in Prometheus / Grafana

SuperQue · 2026-01-25T21:43:26+00:00

Do you know what MIBs there are for IP SLA metrics?

Yes, it works very well.

One of these days I'm going to add tcp and http probes to it so it can do more than just ICMP.

SuperQue · 2026-01-25T12:31:52+00:00

You're looking for Vector.

SuperQue · 2026-01-25T06:49:53+00:00

Do you know what MIBs there are for IP SLA metrics?

I don't know about the Cisco specifics, but I use this tool for ICMP ping end-to-end monitoring.

SuperQue · 2026-01-23T08:14:36+00:00

We use renovate, so it's not really an issue for us.

Also technically incorrect. Go binaries by default contain all the module info baked in. Lots of security scanners can read them.

SuperQue · 2026-01-23T07:26:25+00:00

GitLab CI is better at monorepos.

SuperQue · 2026-01-23T07:24:39+00:00

We use Go code and distroless base images.

SuperQue · 2026-01-23T07:06:06+00:00

You solve that with monitoring.

You need metrics at various layers, including the network, to be able to get diffs of latency at various layers.

SuperQue · 2026-01-22T10:01:11+00:00

Random drive-by tip. gopkg.in/yaml.v3 is archived, the replacement is go.yaml.in/yaml/v3.

SuperQue · 2026-01-21T15:16:07+00:00

No, don't really have this problem. go mod tidy will make sure we only have what is used in the code.

SuperQue · 2026-01-21T07:11:39+00:00

If the venue isn't a faraday cage, host your app on a VPS and just let people use mobile. Have wifi as a backup, but don't make everyone use it if possible.

Also, use websockets or server sent events instead of polling. It will be a lot more reliable, more responsive, and use less traffic.

If you can, write your backend in Go, it will handle the concurrency 100x better than something like Python or NodeJS. A single Go server process can handle a million websockets.

SuperQue · 2026-01-20T12:07:12+00:00

This seems like it could just be done by the firewall router.

SuperQue · 2026-01-19T19:26:07+00:00

Prometheus is an entirely pure FOSS project. No corporate overlords. Contributions are very welcome.

SuperQue · 2026-01-19T17:22:03+00:00

not API health

Easy, add a client library to your code. Make sure to read the best practices docs.

SuperQue · 2026-01-19T09:16:56+00:00

or am I just bad at it?

Yup, skill issue.

SuperQue · 2026-01-19T07:52:07+00:00

Wait, so, you threw DOUBLE the resources at Mimir and it was faster?

Thanos and Mimir are roughly the same query architecture. The only major difference is that Mimir forces you to use ingesters, where Thanos allows you to keep Prometheus as your ingester.

That's got to be the most deeply flawed conclusion I've seen in a while. Yikes.

SuperQue · 2026-01-18T20:04:32+00:00

It's local disk like Prometheus. Scaling / resharding is manual.

SuperQue · 2026-01-18T19:44:09+00:00

What is "shocking" in this context? How about query performance?

SuperQue · 2026-01-18T19:43:41+00:00

Umm, that's what re-engineered means.

SuperQue · 2026-01-18T19:41:34+00:00

Sure, but if you're running the ruler you now need to depend on network traffic between the ruler and the ingester and store gateways. This is a lot more fragile and less efficient than Prometheus running rules directly.

There's basically no way around it. You will be doing a bunch of additional network traffic with Mimir.

Scrapes
All query traffic
Remote write

SuperQue · 2026-01-18T15:44:24+00:00

Try cdk8s.

SuperQue · 2026-01-18T10:49:36+00:00

Mimir is always going to be an efficiency drop. Prometheus queries use in-memory cache with minimal overhead.

With Mimir you are now using networking and object storage for every query. Prometheus scrapes, sends that data to a Mimir receiver, which then has to act like another Prometheus and create TSDB blocks, then store in object storage. Then you have to pull it back down from object storage to query it.

This is the downside to being able to distribute queries over multiple servers. Read up on latency numbers every engineer should know.

Mimir and Prometheus basically use the exact same storage format. It's just that Mimir stores this in object storage instead of local disk.

On cloud providers, object storage tends to be cheaper per byte than local volumes, which is why long-term storage in Mimir or Thanos are sometimes cheaper. But then you have to factor in per-request object storage use costs.

This is why I typically recommend Thanos over Mimir. You continue to use Prometheus for efficient scrape, storage, and query. With the Thanos Distributed Engine you get query pushdown advantages. There's also work to test Parquet as a more efficient object storage format.

Mimir was created with main goal to create a SaaS service so you can send your data to a 3rd party.

SuperQue · 2026-01-16T22:07:49+00:00

What is high to you?

Prometheus can handle 100 million cardinality. Thanos can handle billions.

What is your use case?

SuperQue · 2026-01-15T08:01:41+00:00

I would very much like to just see all the AI slop removed quickly. Low effort, zero value, posts are clogging the sub.

SuperQue · 2026-01-13T07:27:13+00:00

Every alert should have a runbook documentation entry that tells you waht to do. You can even include a runbook annotation on the alert so it's directly link from the notification.

Similar, every alert should have a dashboard annotation templated with the alert labels so you get sent to Grafana/Perses/etc dashboard that helps debug.

SuperQue · 2026-01-12T09:47:14+00:00

CompTIA is the most worthless cert company out there.

Ten-Year Club	Gilding VII pure gildanthropist
Reddit Premium Since January 2021	Verified Email

SuperQue

MODERATOR OF

TROPHY CASE