MOMonitoring · Advanced
Community homeHot discussions Latest posts Best of Knowledge base Resources About

Monitoring · Advanced · Newbie question: how should a monitoring-pro config file be organised?

60
MOr/monitoring-pro·posted by alice_dev·5 minutes agoOpen sourcePinned

Newbie question: how should a monitoring-pro config file be organised?

Some background first. Our setup is monitoring-pro plus three downstream services, seven figures of daily requests, peaking around nine in the evening.

The first thing was to collapse the variables. We were changing config and upgrading the version at the same time, and afterwards nobody could say which change caused what. We rolled back to moving one variable at a time, re-ran three times, and only then did the curve settle. Tedious, but not skippable.

Keep it and wait for an official fix44%
Switch to a third-party option now28%
Fork and maintain it ourselves17%
Write an adapter layer and wait11%

102 votes total

13 comments

13 comments

M
Ddev_zhou·12 minutes ago

Worth learning from this debugging approach. We went straight at the logs and took a much longer route.

231
Aalice_dev·5 hours ago

I see point 3 differently. The trade-off depends on your read/write ratio: read-heavy with little writing means caching actually widens the inconsistency window.

181
Sslow_query·3 minutes ago

We have run this in production for two years without hitting it. That said, we never reached this scale, so our experience is not really evidence here.

90
Ttang_hao·2 hours ago

Has anyone run a controlled experiment? I did, reducing it to a single variable, and the difference was 4% — within noise. So I suspect the main cause is something else.

495
Sswoole_leeOP·1 hour agoedited

This matches what we see in production. We only hit it past 3k QPS; the earlier load tests showed nothing — the test traffic was too clean, with no long-tail requests.

5
Bbob_chen·2 hours ago

This is not a monitoring-pro problem, it is a usage problem. The docs say this API is not thread-safe and you must lock around it yourself.

8
Kkernel_panic·12 minutes ago

Agreeing with the above. One addition: with this option enabled the GC count in your metrics doubles, so adjust the alert threshold at the same time or it will keep firing.

88
Zzhu_zong·3 minutes ago

Saved. I am reworking this area this week — this saves a lot of wrong turns.

13
Rran_bo·28 minutes ago

Sharing our numbers, 8 cores 16GB, same scenario:

| Concurrency | P50 | P99 |
|---|---|---|
| 200 | 12ms | 88ms |
| 500 | 31ms | 340ms |

P99 clearly collapses at 500 concurrency, which lines up with your knee point.

1
Zzhou_yi·2 hours ago

I just read the monitoring-pro source — the author actually explains the reasoning in a comment, roughly "so that it degrades into predictable behaviour in extreme cases".

25
Hhuang_keMod·28 minutes ago

A question: what changes in a container with a 512Mi memory limit? That is how we run it in production.

5
Bbob_chen·2 hours ago

Can you give a minimal reproduction? I ran it locally for ten minutes and could not reproduce on macOS with the latest version.

6
Ddev_zhou·2 hours ago

Thanks for sharing real numbers — far more useful than the articles that only cover concepts.

1

This is the post detail page /en/c/monitoring-pro/post/p0. Posts and comments are generated deterministically from a seeded PRNG, so the same post always renders the same content and the link can be shared, reloaded and indexed. In production this page reads MySQL for the post, Redis for hot-post caching, and fetches the whole comment tree in a single query on the path column.

See the database schema →