Plugin incompatible with OpenTelemetry InfluxDB Receiver?

[perrinj3]

When trying this plugin to send Jmeter results to an InfluxDB Receiver in the OpenTelemetry Contrib Collector the results are rejected with a HTTP response code 400. Is there any intention to support this connectivity? I had a look at the error and it seems to be related to the Measurement Names this plugin uses but there may be other issues

[mderevyankoaqa]

Hi @perrinj3, the plugin was not used with OpenTelemetry InfluxDB, no tests were performed to check that compatibility.

Can you please share any docs to read how OpenTelemetry InfluxDB Receiver is used and why?

BR,
Mike

[perrinj3]

Hi Mike Thanks for the response. We use an OpenTelemetry collector to receive metrics from K6 and JMeter for export to both InfluxDB and Prometheus (and then visualisation with Grafana). We chose the Influxdb Receiver for the OpenTel collector as both K6 and JMeter can export using the influxdb line protocol. Refer to https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/influxdbreceiver This works fine for K6 and many Jmeter Backend listeners but in your case I think there is an issue in how Opentelemtry selects the correct schema. I think with your backend listener the measurement needs to be set to “prometheus” so the OpenTel receiver can select the correct schema. If I change the JMeter Plugin code for measurement from “rawResults” to “prometheus” it works fine. We’d really like to use your plugin as it has many great features. The other thing we do is run OpenTelemetry in an Openshift container and the destination port is exposed in the endpoint. Ie we don’t specify the port in the Backend Listener configuration , just the url. I couldn’t see a way to not specify the port in your BEL. It defaults to 8086 is no port is specified. I changed the code to remove this but it would be good to have the option for no port as there must be other people using OpenShift. I’m trying to get a response from OpenTel about the receiver but no luck so far. Any advice or help would be appreciated Regards, John From: Mike Derevyanko ***@***.***> Sent: Monday, November 14, 2022 9:50 PM To: mderevyankoaqa/jmeter-influxdb2-listener-plugin ***@***.***> Cc: John Perrin ***@***.***>; Mention ***@***.***> Subject: Re: [mderevyankoaqa/jmeter-influxdb2-listener-plugin] Plugin incompatible with OpenTelemetry InfluxDB Receiver? (Issue #78) Hi @perrinj3<https://github.com/perrinj3>, the plugin was not used with OpenTelemetry InfluxDB, no tests were performed to check that compatibility. Can you please share any docs to read how OpenTelemetry InfluxDB Receiver is used and why? BR, Mike — Reply to this email directly, view it on GitHub<#78 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASE3UA2UXJRCDQWPJUDQM2TWIIKLXANCNFSM6AAAAAAR3554XE>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>> This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ Bank New Zealand Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication.