zmstone
zmstone
@jli113 could you enable debug level log to inspect what happened to the client ? see log level config here: https://docs.emqx.io/en/broker/v4.3/getting-started/log.html#log-trace
Are all the clients from telegraph? if not, could you point out which one?
Thank you for the updated logs There are only a few warnings What’s the observed/expected behavior one the client side?
> [outputs.mqtt] Wrote batch of 139 metrics in 7.262254819s [outputs.mqtt] Buffer fullness: 139 / 10000 metrics Is this the expected behaviour ? What's the logs from the client which behaved...
I mean what does it log when connecting to emqx
Hi @umeat There is a global `max_subscriptions` configuration, but not per client control. I have labeled it with as a feature request. I am not quite sure about the priority...
It's odd to see the below log. which mosquitto version did you use? ``` 2022-08-10T12:32:54.093Z | 1660134751: Client bridge:mqtt:mosquitto_test_broker:2038363:[email protected] disconnected due to malformed packet. ``` I just had a quick...
Hi @fridayy Reasons behind the current design: 1. Avoid many clients bumping one counter concurrently. Arguably we already have a lot of counters bumped concurrently by millions of concurrent clients,...
And thank you for the tip on the documentation, we'll update it.
Hi @cocoaway We are working on it.