OpenTelemetry

We see many devs from Germany are using SigNoz. It would be be good if README is translated to German.

This will make it easier for devs from Germany and German speaking countries to get started with SigNoz.

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

Similar to open-telemetry/opentelemetry-dotnet#2138, we can cut .NET Core 2.1 from support matrix, as .NET Core 2.1 is end of life next month (https://devblogs.microsoft.com/dotnet/net-core-2-1-will-reach-end-of-support-on-august-21-2021/).

Since most of the projects list NETSTANDARD2.0 as the supported one, and not .NETCore2.1, the changes may be minimal, and mostly r

#3615 improves reload behavior by failing with an error rather than hanging, if the config is invalid. This issue tracks creating an automated test to verify this going forward.

(Guessing there's an actual way to make this a test, maintainers will know better ;) )

_Originally posted by @carlosalberto in open-telemetry/opentelemetry-collector#3615 (comment)

It currently is:

private static boolean isKeyValid(String name) { return name != null && !name.isEmpty() && StringUtils.isPrintableString(name); }

It needs to be:
private static boolean isKeyValid(String name) { return name != null && !name.trim().isEmpty() && StringUtils.isPrintableString(name); }

Or it needs to use something like apache StringUtils isBlank.

From this PR open-telemetry/opentelemetry-specification#1729. We had this earlier but removed it since it wasn't part spec at the time of the python 1.0 release. We should add it back.

The TracerProvider::force_flush method is part of the sdk spec but not the api spec.

We have no automatic check for CODEOWNERS on CI.

A CI check can be added so that

1. every component has a CODEOWNERS line and
2. every component folder listed on CODEOWNERS actually exists (to prevent typos).

We're missing retries on Exporter errors: https://github.com/open-telemetry/opentelemetry-specification/blob/318745aaf6fb173eb5cbc887ab76796bd817b3d6/specification/protocol/exporter.md#retry

See open-telemetry/opentelemetry-specification#1492.

In the following code we should check that the links each have a valid span context, and remove any with an invalid span context. https://github.com/open-telemetry/opentelemetry-ruby/blob/f6d156353a838f47daf167156c9b861b7eac2c30/sdk/lib/opentelemetry/sdk/trace/span.rb#L327-L344

Use Case

• Provide a sample application to test DBs, messaging systems and HTTP, GRPC backend resolution and call view.

Proposal

• A simple app where backend can be swapped or we can use multiple backends.

See open-telemetry/opentelemetry-collector-contrib#4277

We need an upgrade routine for v0.31.0 to handle this change. Basically, if this field exists, it has to be removed. Similar to this: https://github.com/open-telemetry/opentelemetry-operator/blob/7250758d04076b0e011b196d10bdea885b84fe80/pkg/collector/upgrade/v0_19_0.go#L47-L52

Actually, opentelemetry-java allows user to customize the metadata in the header, which is convenient to implement our own authentication in collector, any plan for cpp? Thank you.

Is your feature request related to a problem?
No.

Describe the solution you'd like
Provide the ability to customize the gRPC header.

Describe alternatives you've considered
No.

**Additional co

per #268

See socketio/socket.io-website#277

The docs don't say that and maybe the maintainers have a good reason here, but, conceptually, if disconnect and disconnecting are reserved, so is connection.