Add /ping endpoint for compatibility with telegraf/influxdb endpoints

[DaveWK]

Component(s)

receiver/influxdb

Is your feature request related to a problem? Please describe.

Some third party apps utilize a /ping endpoint which is available on telegraf/influxdb and will bail out on sending data when it gets an unexpected ping response (currently for the otel-contrib influxdb receiver it returns 404)

Describe the solution you'd like

Add the /pingto the opentelemetry plugin as an endpoint and have it return 204.
An example curl of telegraf:

curl -vv localhost:8086/ping
*   Trying 127.0.0.1:8086...
* Connected to localhost (127.0.0.1) port 8086 (#0)
> GET /ping HTTP/1.1
> Host: localhost:8086
> User-Agent: curl/8.0.1
> Accept: */*
>
< HTTP/1.1 204 No Content
< X-Influxdb-Version: 1.0
< Date: Thu, 30 Nov 2023 21:16:10 GMT
<
* Connection #0 to host localhost left intact

Describe alternatives you've considered

I tried setting a proxy in front of the endpoint to catch the /ping and return the 204 but it's convoluted to add and support a whole proxy service in an attempt to emulate the native behaviour of a the native telegraf/influxdb rpc

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/influxdb: @jacobmarble

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[jve-engineering]

When I tried to activate the influxdbreceiver as a sink for checkmk, I encountered the same message.

2023-12-03 16:36:48 [5] [influxdb http://192.168.122.166:8086] Successfully initiated connection
2023-12-03 16:36:48 [7] [influxdb http://192.168.122.166:8086] GET /ping
2023-12-03 16:36:48 [3] [influxdb http://192.168.122.166:8086] GET [404] 404 page not found

2023-12-03 16:36:48 [5] [influxdb http://192.168.122.166:8086] Closing connection

I have added the /ping endpoint and tested it successfully with checkmk. If the changes are acceptable, I would like to open a pull request.

[jacobmarble]

@jve-engineering LGTM!

[crobert-1]

Removing the needs triage label as the code owner supports the idea.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/influxdb: @jacobmarble

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[mx-psi]

I believe this was fixed by #29662