OpenTelemetry

Bug description

Please describe.
If this affects the front-end, screenshots would be of great help.
in the development environment if we make any change. change is not reflected over the browser

Expected behavior

change should be reflected immediately without manually refreshing the page

How to reproduce

you can change any text

Thank you for your bug repor

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.

Environment:
Python 3.7.9, Ubuntu 20.04
opentelemetry-api 1.4.0
opentelemetry-sdk 1.4.0
flask 1.1.3
requests 2.26.0

Setup: A flask upstream server (to set_baggage) and downstream server (to get_baggage).
Attached requirements.txt if any additional dependency information is needed

**Steps to

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 need to implement the Links functionality in the specification:

https://github.com/open-telemetry/opentelemetry-specification/blob/b46bcab5fb709381f1fd52096a19541370c7d1b3/specification/overview.md#links-between-spans

@zsistla mentioned she'd like to tackle this.

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.

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:

Currently, we introduced a docs file for details on otelcol custom resource spec this needs to be manually maintained for all changes on CRD spec. So we should find an efficient way to generate the docs from CRD.

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

typeorm tests are creating a new db connection in each test. If something goes wrong (assertion fails, exception thrown), the test does not close this connection which causes the following tests to fail as well.
We need to move the logic into afterEach hook so tests clean the environment after they are done for whatever reason.

Currently we can access logs, traces and metrics locally. Could you explain how to integrate it with Grafana cloud?