I’m tying to consume MQTT topics that have varying data types (data_format = "value"). I saw this post: https://community.influxdata.com/t/mqtt-consumer-with-multiple-value-types/5666/5 It seems that I need to create an mqtt_consumer for each set of topics with a given data type. When I try to do t…

Is this with Telegraf 1.9? I would be surprised if 2 connections was enough to trigger MQTT to close the connection. The plugin is using the data format system to parse messages, which only allows for a single parser configuration per plugin. I think it would be possible to create a data_type = "…

I can see this as a potential problem with the multiple plugin method, how many plugins do you have defined and what MQTT broker are you using?

I’m currently trying this with just two MQTT plug-ins connecting to the same mosquitto broker. Long term, it seems that it would be best to have the ability to define data types with each topic in a single plug-in definition. I have not looked at this plug-in code. If you are familiar with it, can y…

Thanks, @daniel . I’m new to Telegraf and am not aware of all the possibilities. This looks promising. I’ll play with it.

@daniel , thanks for the pointers here. I think this could work but I’m now hitting type conflicts when writing to Influx. I’m trying to understand the converters but I don’t see any documentation on things like “namepass” and “tagpass”. Can you point me to the relevant info? In a specific case, I’…

Here is a link to the metric-filtering documentation, check the examples lower on the page as well. When a metric is selected (namepass/tagpass/etc) the conversions will take place, if it is not selected it will be skipped and the next processor will have a chance to handle it. You are able to con…

Thanks, @daniel . I’ll look at the documentation. It seems that my experience is not matching what you stated. I changed your example so that both converters were integer = .... The MQTT topic that was originally an integer (no decimal in the string) gets written to the DB just fine but the float top…

I read through the metric-filtering documentation. Do I understand correctly that I could combine the two converters under one namepass = "mqtt_consumer" if I’m trying to convert everything to an integer? I just tried this and now see this error in the log any time a float value comes in: [process…

Sorry, I must have been testing it incorrectly, it can’t handle numeric strings with decimal part. I opened 5518 with a fix, we can include it in 1.10.0 which is coming out soon. This also adds the usual rounding to the conversion (2.5 → 3).

Multiple mqtt_consumer

Telegraf

trpropst March 3, 2019, 3:23pm 11

Thanks, @daniel. That should resolve my issue.

Topic		Replies	Views
Single MQTT Consumer for int, float & string? Telegraf mqtt	4	1712	October 27, 2022
MQTT consumer multiple types topic_parser Telegraf telegraf , types , mqtt	1	2075	April 29, 2022
Telegraf as MQTT consumer - handling string and float values Telegraf telegraf , kapacitor , iot	10	16174	October 10, 2021
MQTT Consumer Topic Parsing with Value data format? Telegraf influxdb , mqtt	4	986	November 29, 2022
Telegraf MQTT Consumer telegraf	4	5074	June 2, 2020

Multiple mqtt_consumer

Related topics