In an effort to make finding the state of each component easier, the README for each component should contain a table which includes:

• stability level
• supported pipelines
• distributions which contain the component

See open-telemetry/opentelemetry-collector-contrib#10006 for an example table with embedded links:

| Status                   |           |
|

Bug Report

If you use the B3 propagator with e.g. the Grpc.Core instrumentation then it fails to connect the parent spans to the new server spans because gRPC headers are always lower case.

The issue is that the B3 propagator does not store the headers as lower case and then this line in the Grpc.Core instrumentation does not do case-insensitive comparison: https://github.com/open-telemetry/

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

• This only affects the JavaScript OpenTel

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.

There are many places to add tests with ”gtest_add_tests“, But gtest_add_tests is a new feature of Cmake 3.9 version, When I try to compile with 3.8.5, it doesn't compile the test code anyway, this confused me for a while.

We have a sprinkling of otel.foo kinds of tags being used throughout the codebase:

opentelemetry-ruby on  ahayworth/add-dropped-counts-zipkin-jaeger via 💎 v3.1.1
zsh ❯ git grep 'otel\.' | egrep -v '\/test\/'
exporter/jaeger/lib/opentelemetry/exporter/jaeger/encoder.rb:          tags << encoded_tag('otel.dropped_attributes_count', dropped_attributes_count) if dropped_attributes_count.p

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