telemetry

Since we upgraded to latest gaurav-nelson/github-action-markdown-link-check@1.0.14 (from 1.0.13) every time we change something in a md file with links we fail the link check, see:
https://github.com/open-telemetry/opentelemetry-collector/runs/5755269731?check_suite_focus=true

Something that may be related open-telemetry/opentelemetry-specification#2426.

Today our AspNetCore metrics instrumentation captures a small subset...

https://github.com/open-telemetry/opentelemetry-dotnet/blob/96b043e35fcf407147a9ad9c4fae2b6915f3a9ab/src/OpenTelemetry.Instrumentation.AspNetCore/Implementation/HttpInMetricsListener.cs#L58-L61

...of the attributes defined in the [spec semantic conventions](https://github.com/open-telemetry/opentelemetry-specification/bl

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

e.g. I'm looking at @opentelemetry/instrumentation-http I see instructions on how it can be setup, but I don't see any documentation on the produced outcome.

What are the telemetry properties generated? Where can I find reliable documenta

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.

This would be eventually required for

• To support async interface between span/log processor and exporters.
• Async IO while exporting the spans.
• Timers to poll for Spans in BatchSpanProcessor, and metrics in PeriodicMetricReader.
• Asynchronously collect metrics for all the instruments across all the meters ( this would be a costly operation sequentially or even using threads).

Re

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:

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