Failed to export batch code: 204, reason: Failed to export batch code: 204, reason:

[bhavya-giri]

from phoenix.otel import register
from openinference.instrumentation.llama_index import LlamaIndexInstrumentor

tracer_provider = register(
project_name="default", endpoint="my-url"
)

LlamaIndexInstrumentor().instrument(tracer_provider=tracer_provider)

[dosubot[bot]]

The error "Failed to export batch code: 204" occurs because Phoenix was incorrectly returning a 204 No Content status code instead of the required 200 OK status code for successful OTLP trace exports. This issue has been resolved in Phoenix PR #5962. You might want to update your Phoenix package to the latest version where this issue is fixed.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[bhavya-giri]

@dosu, upgraded the packages to latest still getting the same error

[dosubot[bot]]

If you're still encountering the "Failed to export batch code: 204" error after upgrading, here are a few steps you can take to troubleshoot the issue:

1. Verify the Upgrade: Ensure that the Phoenix package has been successfully upgraded to the version where the fix was implemented. You can check the installed version using pip show arize-phoenix and compare it with the latest release.

2. Check Configuration: Double-check your configuration settings, especially the endpoint URL in the register function. Ensure that it is correct and accessible.

3. Logging: Increase the logging level to debug to gather more detailed information about what might be going wrong. You can set the environment variable PHOENIX_LOGGING_LEVEL to debug to get more insights.

4. Network Issues: Ensure there are no network issues or firewalls blocking the connection to the specified endpoint.

5. Dependencies: Verify that all dependencies are up-to-date and compatible. Specifically, check the versions of opentelemetry and openinference packages.

If the issue persists after these checks, there might be a need to look deeper into the specific configuration or environment setup.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[axiomofjoy]

Hey @bhavya-giri, thanks for using Phoenix, and sorry you're hitting this issue. Can you tell me more about your deployment, in particular, what version of Phoenix are you using client-side and server-side, are you running with Docker, etc.?