You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
judahrand opened this issue
Jun 25, 2024
· 1 comment
Labels
bugSomething that is supposed to be working; but isn'tcoreIssues that should be addressed in Ray CoreP1Issue that should be fixed within a few weeksserveRay Serve Related Issue
The text was updated successfully, but these errors were encountered:
judahrand
added
bug
Something that is supposed to be working; but isn't
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
labels
Jun 25, 2024
anyscalesam
added
P1
Issue that should be fixed within a few weeks
serve
Ray Serve Related Issue
core
Issues that should be addressed in Ray Core
and removed
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
labels
Jul 1, 2024
@judahrand - yeah we're aware - working on restoring Open Telemetry working again. Would you be interested in contributing; we're working on an RFC that we'll publish but need help in implementing.
bugSomething that is supposed to be working; but isn'tcoreIssues that should be addressed in Ray CoreP1Issue that should be fixed within a few weeksserveRay Serve Related Issue
What happened + What you expected to happen
When enabling tracing on a Ray Serve deployment I get an error:
I'd hoped that tracing would just work with Ray Serve so that I could set up OTEL traces.
Versions / Dependencies
ray==2.30.0
Reproduction script
Issue Severity
High: It blocks me from completing my task.
The text was updated successfully, but these errors were encountered: