opentelemetry-ruby icon indicating copy to clipboard operation
opentelemetry-ruby copied to clipboard

OpenTelemetry Ruby API & SDK, and related gems

Results 261 opentelemetry-ruby issues
Sort by recently updated
recently updated
newest added

Ruby 3.1 is no longer receiving updates as of (31 Mar 2025)

Deprecate jaeger exporters: https://github.com/open-telemetry/opentelemetry-specification/pull/2858 Migration to OpenTelemetry SDK: https://www.jaegertracing.io/sdk-migration/ Related: https://github.com/open-telemetry/opentelemetry-ruby/issues/1962#issuecomment-3555975297

@wsmoak brought up some great points about the timeout behavior for asynchronous metrics in #1877. Some things to ponder: 1. Currently, the asynchronous timeout is using [Ruby's Timeout](https://ruby-doc.org/3.4.1/stdlibs/timeout/Timeout.html) class, which...

metrics
keep

We've recently looked into adding a custom SpanProcessor to most of our applications. We need integrate with a particular vendor that doesn't fully/truly support OpenTelemetry specifications and relies on setting...

stale

If an Exporter returns a FAILURE status, the BatchSpanProcessor calls `OpenTelemetry.handle_error` with a new exception. But that exception doesn't tell you anything about what happened: all we get back is...

stale

Currently the SDK supports `create` methods like `create_counter` and `create_observable_gauge`. Once created however, it seems there is no way to retrieve them. You must keep a reference to the instrument...

metrics
keep

I am seeing this error occasionally despite already aggressively sanitizing output before logging. I'm using the latest releases of all the gems and haven't been able to intentionally reproduce it....

keep
logs

See if we can take advantage of shorter intervals to reduce or eliminate the sleeps in the metrics SDK test suite

metrics
keep

[OTLP Specification 1.7.0](https://opentelemetry.io/docs/specs/otlp/#otlphttp-request) > The default URL path for requests that carry profiling data is /v1development/profiles and the request body is a Protobuf-encoded ExportProfilesServiceRequest message. Java implementation: https://github.com/open-telemetry/opentelemetry-java/tree/main/exporters/otlp/profiles/src/main/java/io/opentelemetry/exporter/otlp/profiles

keep