I've just updated my "demo" application to the release
0.8.0 and I've faced some issues. I was using
trace_id = OpenTelemetry::Instrumentation::Sinatra::Instrumentation.instance.tracer.current_span.context.trace_id.unpack('H*')
to get a trace_id but structure has been changed and right now
current_span is not reachable. Could you please tell me how can I get current span or point some docs? And one more thing, how can I add an event to the span?
require 'opentelemetry-sdk' require 'opentelemetry-propagator-b3' OpenTelemetry::SDK.configure do |c| c.http_extractors = [OpenTelemetry::Propagator::B3::Single.rack_extractor, OpenTelemetry::Propagator::B3::Multi.rack_extractor] c.http_injectors = [OpenTelemetry::Propagator::B3::Single.rack_injector] c.text_map_extractors = [OpenTelemetry::Propagator::B3::Single.text_map_extractor, OpenTelemetry::Propagator::B3::Multi.text_map_extractor] c.text_map_injectors = [OpenTelemetry::Propagator::B3::Single.text_map_injector] end
Hey folks. There was an action item that came out of the maintainers meeting. We have been asked to:
Perhaps we can try to read through the OTEP before our SIG meeting tomorrow and make some time to discuss how we'd like to handle things and what to put in our draft.
railsinstrumentation and b3 propagation has hit (stuck with B3 as long as Istio/Envoy is using it). I see now that I get a
Rackroot span when I do a use_all. After that, all the
redisspans get nested drive the stack too deep and everything is an error. Is this the result of open-telemetry/opentelemetry-ruby#352
main. Existing pull requests, the CI and release configurations, and documentation links that point back at the GitHub tree, have all been updated accordingly. When you visit the repo on GitHub, it will show a popup with instructions for updating your local clone. Additionally, if you have a fork of the repo, you may consider updating its default branch name as well to avoid confusion. Feel free to ping me if you have problems/questions.
SimpleSpanProcessorI'm getting an error during span export
OpenTelemetry error: unexpected error in span.on_finish - undefined methodexport' for #<Hash:0x00007f954acc1a50>`
export OTEL_RESOURCE_ATTRIBUTES=service.name=testdoesn't work - I'm getting
otlp.instrumentation.library.nametag with value
OpenTelemetry::Instrumentation::Railsbut it's reporting
OpenTelemetry::Instrumentation::Rack. I'm not an Ruby expert but I would like to know if Rails instrumentation is really working :)
Could not find gem 'opentelemetry-api (~> 0.13.0)', which is required by gem 'opentelemetry-propagator-jaeger', in any of the relevant sources: source at../../api`` Any thoughts on what I can look into? This is a pattern used in many of the Gemfiles in the repo and I can't reproduce this issue locally
:wave: Hi all - I had a question. I need to redact potentially sensitive data from exceptions recorded on spans, but for a variety of reasons cannot run a collector at this time - the scrubbing needs to be done in-process. I was wondering if anyone had any advice on the best approach to do this?
My ideal case would be that our developers can continue to call
span.record_exception(error_object), and we scrub attributes before any exporter gets involved. But I'm not sure where I should hook into the pipeline:
Any advice you have is appreciated :)