8b060a75f1
https://emqx.atlassian.net/browse/EMQX-8548 Currently, we face several issues trying to keep resource metrics reasonable. For example, when a resource is re-created and has its metrics reset, but then its durable queue resumes its previous work and leads to strange (often negative) metrics. Instead using `counters` that are shared by more than one worker to manage gauges, we introduce an ETS table whose key is not only scoped by the Resource ID as before, but also by the worker ID. This way, when a worker starts/terminates, they should set their own gauges to their values (often 0 or `replayq:count` when resuming off a queue). With this scoping and initialization procedure, we'll hopefully avoid hitting those strange metrics scenarios and have better control over the gauges. |
||
|---|---|---|
| .. | ||
| i18n | ||
| include | ||
| src | ||
| test | ||
| .gitignore | ||
| docker-ct | ||
| README.md | ||
| rebar.config | ||
emqx_ee_bridge
An OTP application
Build
$ rebar3 compile