I think I've had about a 10% success rate with markdownlint since it seems to get throttled by GitHub. I've heard this was an issue that should have improved, but it doesn't seem to have been and I can't find any context for that in this repo.

Perhaps switching markdownlint to a GitHub Action would work around the throttling "for free" (actions automatically have GitHub creds for the repo). Jus

After the merge of this PR: open-telemetry/opentelemetry-dotnet#1548

We should create more unit tests just like open-telemetry/opentelemetry-dotnet#1537 to validate the full behavior.

Is your feature request related to a problem? Please describe.
ARM64 Macs should be able to run the Collector from a container image without needing to manually build.

Describe the solution you'd like
Build Collector for darwin/arm64

Additional context
golang/go#38485 is slated to go out with go1.16, which is a prereq.

Resource object attached to a span should contain service name in labels:
https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/data-resource-semantic-conventions.md#service

This service name could be used as Jaeger service name. The service name is a required parameter to create Jaeger GRPC exporter. We could relax this requirement and set the service to `u

As per spec:

OpenTelemetry resources MUST be mapped to Jaeger's Span.Process tags. Multiple resources can exist for a single process and exporters need to handle this case accordingly.

See more details: https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/trace/sdk_exporters/jaeger.md#resource

See the spec change for details open-telemetry/opentelemetry-specification#1186

Is your feature request related to a problem? Please describe.
Leverage the kinesisexporter to export otlp protobuff to kinesis streams. Currently, the format is fixed to the jaegar/zipkin format. In a more general sense, we would like support for format-agnostic, where specific data formats can be published by implementing marshaller classes.

Describe the solution you'd like
Use the

Adding instrumentation feature to opentelemetry-php to sdk mentioned here: https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/trace/sdk.md#additional-span-interfaces

While working for OTLP/GRPC , it requires Instrumentation library in sdk for dealing with proto files

Something like this : [opentelemetry-go reference ](https://github.com/open-telemetry/ope

Renovate bot hasn't been updating Go packages. And it seems a lot of our errors in logs stem from outdated Go dependencies:

0. Version control gopkg.lock/toml is deprecated. We should update to use Go.mod/sum. This might be why renovatebot isn't catching updates for go?

1. A lot of errors happen in go containers during provisioning, example:

WARNING: Package "github.com/golang/protob

When you click across the top nav we have inconsistencies for the About, and Docs.

The other pages have a separator like this:

We should do the same across the pages we control. Obviously the Blog on Medium is going to have a different nav.

See: open-telemetry/opentelemetry-specification#962

Propagators to be used as a comma separated list.

Default is "tracecontext,baggage".

Known values for OTEL_PROPAGATORS are: "tracecontext", "baggage", "b3", "jaeger"

The operator knows about a few receivers, but I'm not sure this list is up to date:
https://github.com/open-telemetry/opentelemetry-operator/tree/master/pkg/collector/parser

This ticket is to sync this list.

We should add a badge to the readme in order to know what is the latest version 👍