telemetry

Once this spec PR is merged, we might want to borrow the idea and do similar thing in this repo.

Consolidating thread on all open plugin requests.

All issues need help if you'd like to contribute to the project 😃

The documentation on writing a plugin can be found here.

• Umami DavidWells/analytics#149
• Firebase DavidWells/analytics#133
• Plausible https://gith

https://open-telemetry.github.io/opentelemetry-js/

I clicked "SDK docs" in the readme, which took me to https://open-telemetry.github.io/opentelemetry-js/

There, I opened both the getting started guide and the node auto-setup thing in this paragraph:

To get started tracing your own application, see the Getting Started Guide. For more information about automatic instrumentation see @OPEN

For some uses cases it would be useful to have an option in the gr_satellites command line tool that skips the demodulator and sends the input the directly to the deframer.

as mentioned in the UPDATING file, there are some domains in the list that represent the same domain but differ by a commonly confused character (like dashes, em dashes, and en dashes). Theres also a few that look like two characters smushed together (I think there's one like that for fi in a couple places). These are likely due to copy-paste errors or from parsing the PDF, however I want to be

Our Rack instrumentation allows configuration of a URL quantization function https://github.com/open-telemetry/opentelemetry-ruby/blob/1c37b00dc82d490dace1f92739977aa4674d7039/instrumentation/rack/lib/opentelemetry/instrumentation/rack/middlewares/tracer_middleware.rb#L122-L137

We should add the same functionality to the Sinatra instrumentation. @genebean reported this requirement in Gitter:

Add support for configuring OtlpHttpExporter using environment variables defined by specs:
https://github.com/open-telemetry/opentelemetry-specification/blob/v1.0.0/specification/protocol/exporter.md