zmstone
zmstone
For docker, tune host instead.
Latest EMQX v5 (v5.5.0) behaviour: For MQTT v5 clients, the server sends `DISCONNECT` packet with error code `RC_ADMINISTRATIVE_ACTION` (or `0x98`, or `152`). For MQTT v3 clients, the server close the...
rule ID is now available in `metadata` in v5. here is an example from 5.5: `metadata => #{rule_id => }` ``` [rule action] rule_xlu4 Action Data: #{flags => #{dup =>...
this is not something we can fix as the events are independent especially when the client changes clientid.
Sorry for the delayed update. There is a task in the backlog. for internal ref: [ER-245](https://emqx.atlassian.net/browse/ER-245)
seems to be answered by Rory, but no feedback for a long time.
This is exactly the message replay feature being developed for EMQX Enterprise edition. Stay tuned
Closing this issue due to lack of input. For anyone who encounters the issue as originally reported, please use the debug/trace (from dashboard UI) to trace the telegraf client and...
Maybe a good alternative is to add a `update_metric` rule action which bumps a counter (register if not exist), and export this counter from Prometheus.
It is now supported in EMQX v5. for example (based on v5.5):