[ENHANCEMENT]: add a no-op handler for OTLP metrics and logs until they are supported

[codefromthecrypt]

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

I have instrumentation that sends logs, metrics and traces. Phoenix currently only accepts traces on its HTTP port 6006. So, you get errors like this.

INFO:     172.17.0.1:36834 - "POST /v1/metrics HTTP/1.1" 405 Method Not Allowed
INFO:     172.17.0.1:36846 - "POST /v1/traces HTTP/1.1" 200 OK
INFO:     172.17.0.1:36854 - "POST /v1/logs HTTP/1.1" 405 Method Not Allowed
INFO:     172.17.0.1:36866 - "POST /v1/metrics HTTP/1.1" 405 Method Not Allowed
INFO:     172.17.0.1:36882 - "POST /v1/traces HTTP/1.1" 200 OK

Describe the solution you'd like

While 405 is correct, it isn't a great experience for something expected to not work. I'd suggest a no-op handler so that it is 200s even though the data is tossed.

Describe any alternative solutions you've considered

Alternatively, or in addition to this, support the other signals.

Additional context

No response

Social Media Handle

https://x.com/adrianfcole

[cephalization]

Hey @codefromthecrypt we've been discussing support for metrics and will re-visit this ticket when we make a decision regarding them. Thanks for bringing this to our attention

[dosubot[bot]]

Hi, @codefromthecrypt. I'm Dosu, and I'm helping the Arize Phoenix team manage their backlog and am marking this issue as stale.

Issue Summary:

• You requested adding a no-op handler for OTLP metrics and logs in Phoenix to avoid 405 errors.
• Suggested options included discarding data with a 200 OK response or providing full support for these signals.
• The maintainer acknowledged the request and mentioned ongoing discussions about metrics support.
• No further updates or decisions have been shared since then.

Next Steps:

• Please let me know if this issue is still relevant with the latest version of Arize Phoenix by commenting here.
• If I don’t hear back within 7 days, the issue will be automatically closed.

Thanks for your understanding and contribution!

[codefromthecrypt]

I think this is really still a UX win for normal otel stuff vs having to explicitly add env vars like this:

# Phoenix does not support OTLP metrics or logs
OTEL_METRICS_EXPORTER=none
OTEL_LOGS_EXPORTER=none

For example, I had to add these even though there's no docs yet to say you need to here: https://github.com/envoyproxy/ai-gateway/issues/1121

@mikeldking is this a help wanted type of thing, or a not wanted type of thing? ;)

[dosubot[bot]]

Thanks for confirming, @codefromthecrypt! @mikeldking, could you please take a look and advise if this is something we want to pursue as a help wanted item?