Hello! I’m trying to parse a JSON payload using telegraph json_v2. I’d like to use multiple [[inputs.xxx.json_v2.object]] sections to parse different objects in the payload. However, only the first object is getting parsed and written to InfluxDB. If I add a json_v2.object section for the second…

Hi @whchung - Welcome to the Community Forum! Check the indentation. The example below was copied from working code in my conf file. data_format = "json_v2" [[inputs.http.json_v2]] measurement_name = "something" # TOML subtables for JSON V2 parser [[inputs.http.json_v2.object]] …

Phill, Thank you for your response! Yes, I used the JSON Playground to verify my paths. Your example shows more than one json_v2.object section with more than one path. So it looks like using more than one json_v2.object section should work :+1:. I’ll try this again, following your example with…

Can each of the json_v2.object sections have a different tag definition? Also, what does the indentation look like if I’m using mqtt_consumer with additional subsections, such as topic parsing? I tried the snippet below using the indentation from your example with no luck. The second json_v2.obje…

Interestingly, using a single json_v2.object definition works. At least I get tags for both objects. I needed to specify the tags using a path prefix with _, not ., as the separator. I’m now wondering again if using two json_v2.object definitions is a problem, especially with the mqtt_consumer pl…

@whchung [image] whchung: [[inputs.mqtt_consumer.json_v2]] measurement_name = "something" # TOML subtables for JSON V2 parser [[inputs.http.json_v2.object]] Be careful - This is mixing inputs.mqtt with inputs.http which won’t work. All TOML subtables below the initial [[inputs.…

@phill Sorry, I’m using inputs.mqtt_consumer with everything, with no http. The mixing in my example was a copy/paste error :blush:. So I’m really using something like the snippet below. I never get tag “anotherMyTag” to show up unless I only use one [[inputs.mqtt_consumer.json_v2]] section and t…

@phill I appreciate the pointer. I looked at the post you referred to. It’s using two different MQTT brokers, so I can understand why using two different mqtt_consumer plugins makes sense. The post also uses mqtt_consumer.topic_parsing to generate tags, not the json_v2 parser. It dumps the enti…

@whchung I use mqtt to relay sensor data to Home Assistant but I haven’t used the [[inputs.mqtt_consumer]] plugin. So there’s the JSON payload inside an mqtt wrapper (the topic) and I assume the topic_parsing is required to unwrap and get to the payload. I think you could remove the tags = "_/_/_/…

I gave up trying to define multiple [[inputs.mqtt_consumer.json_v2.object]] sections. It really does look like only one will work. To define fields, I just wrote out multiple `[[inputs.mqtt_consumer.json_v2.field]] sections to define each of the fields I wanted. This was not as elegant as being t…

Json_v2 parsing multiple objects in same payload results in ignored objects

Telegraf

phill July 18, 2022, 11:43pm 8

@whchung
Take a look at this post. If you can’t get everything to work in 1 plugin, you can split it up into more. Also mqtt_consumer parsing is discussed in more detail.

Topic		Replies	Views
Json_v2 how to have all elements in "tags" object added as tags? Telegraf json , parser	3	2148	May 16, 2023
JSON v2 parsing - variable string inside path Telegraf json	4	143	December 16, 2025
Help with json_v2 object of objects parsing Telegraf	2	982	March 21, 2023
JSON parsing help Telegraf telegraf , json	8	1129	February 26, 2022
Correct way to configure json_v2 with mqtt_consumer Telegraf telegraf , mqtt , json	3	1084	October 8, 2024

Json_v2 parsing multiple objects in same payload results in ignored objects

Related topics