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.

If a prometheus receiver, fails to scrape an endpoint, the output shows something like:

2021-01-12T21:11:10.496Z	warn	internal/metricsbuilder.go:104	Failed to scrape Prometheus endpoint	{"component_kind": "receiver", "component_type": "prometheus", "component_name": "prometheus", "scrape_timestamp": 1610485870495, "target_labels": "map[instance:aks-agentpool-30099824-vmss000002 job:cadviso

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

MyPy 0.800 is out. It finally supports namespace packages properly and we can remove the placeholder __init__.pyi files in a few spots.

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

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

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

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

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"

Enable requests served by Nginx server for distributed tracing via Opentelemetry api/sdk, and contribute it to opentelemetry-cpp-contrib repo.

Reference:

1. Creating dynamic modules for nginx: https://www.nginx.com/blog/compiling-dynamic-modules-nginx-plus/#obtain-module
2. Opentracing nginx module: https://github.com/opentracing-contrib/nginx-opentracing

When installing the operator in new Kubernetes versions, the following warnings are shown:

Warning: apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition

Warning: rbac.authorization.k8s.io/v1beta1 ClusterRole is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v

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