Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for schema_url #1708

Open
3 tasks
kaylareopelle opened this issue Aug 29, 2024 · 1 comment · May be fixed by #1719
Open
3 tasks

Add support for schema_url #1708

kaylareopelle opened this issue Aug 29, 2024 · 1 comment · May be fixed by #1719
Assignees
Labels
keep metrics spec-compliance Required for OpenTelemetry spec compliance

Comments

@kaylareopelle
Copy link
Contributor

The schema_url feature is not currently available for the Ruby OpenTelemetry project. Tracers, Meters, and Loggers could use the feature.

Telemetry schemas help with alignment among OpenTelemetry semantic conventions, telemetry sources, and telemetry consumers.

We could consider supporting schema_url for multiple signals at once, or just for one at a time. Note that schema_url is not optional for metrics, but is for traces and logs.

@kaylareopelle kaylareopelle added spec-compliance Required for OpenTelemetry spec compliance metrics labels Aug 29, 2024
Copy link
Contributor

github-actions bot commented Oct 5, 2024

👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this issue will be closed eventually by the stale bot.

@github-actions github-actions bot added the stale label Oct 5, 2024
@kaylareopelle kaylareopelle added keep and removed stale labels Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
keep metrics spec-compliance Required for OpenTelemetry spec compliance
Projects
Status: In Review
Development

Successfully merging a pull request may close this issue.

2 participants