You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The MQTT plugin would report data up to the server in friendly way for reduced traffic/storage and easier parsing by industry standard MQTT subscribers. For example:
The MQTT Plugin sends data with a unix timestamp on EVERY value - for complex installs this results in massive overhead, plus most MQTT installs don't use this information and drop it on the floor. In fact, most installs use the time of arrive for most reporting and charting. Additionally, most MQTT tools (eg: MQTT Explorer) are unable to parse this format preventing things like charts from being displayed. I understand this is a common method which collectd uses, but the MQTT world doesn't.
Expected behavior
The MQTT plugin would report data up to the server in friendly way for reduced traffic/storage and easier parsing by industry standard MQTT subscribers. For example:
collectd/bob/memory/memory-wired 1714962432
collectd/bob/memory/memory-active 9526575104
Actual behavior
The MQTT Plugin sends data with a unix timestamp on EVERY value - for complex installs this results in massive overhead, plus most MQTT installs don't use this information and drop it on the floor. In fact, most installs use the time of arrive for most reporting and charting. Additionally, most MQTT tools (eg: MQTT Explorer) are unable to parse this format preventing things like charts from being displayed. I understand this is a common method which collectd uses, but the MQTT world doesn't.
collectd/bob/memory/memory-wired 1448840558.555:1714962432
collectd/bob/memory/memory-active 1448840558.555:9526575104
I would like to propose an option which could be placed in the collectd.conf file which would disable all of these unix timestamps on every value.
Steps to reproduce
The text was updated successfully, but these errors were encountered: