OpenTelemetry

Is your feature request related to a problem?

The first step towards app optimization

Please describe.
Configure whyDidYouRender under the development env

**Note: make sure it is compatible with all the custom hooks that we are using in the project **

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

The Kubernetes example config is currently using the old squashed TLS configuration, which causes pods to fail with:

2021-10-22T11:44:16.540Z	info	service/collector.go:303	Starting otelcol...	{"Version": "v0.33.0-50-g0594aa1a", "NumCPU": 6}
2021-10-22T11:44:16.540Z	warn	service/collector.go:312	`mem-ballast-size-mib` command line option has been deprecated. Please use `ballast extension` 

InMemoryExporter is designed for unit test purpose.

If OpenTelemetry .NET unit tests have some common need that cannot be achieved by InMemoryExporter, we would want to fix it in InMemoryExporter rather than inventing another exporter for tests.

The ask is to evaluate whether it is possible to get rid of https://github.com/open-telemetry/opentelemetry-dotnet/blob/0c93744d4ba51676b61ab1

In the doc page https://opentelemetry.io/docs/java/manual_instrumentation/, it would be nice if a layer could be added, using the latests dependencies, bom and inner project dependencies(api, sdk, and opentelemetry-exporters-otlp) to use the provided code.

It would be nice if the sample could provide the gradle/maven, etc. dependencies as a block to copy/paste int the https://opentelemetry.io/

The recently added flags in timescale/promscale#578 are yet to be updated in prom-migrator's readme which can be found here.

The generate Github Action checks if any code generation scripts were missed by the contributor and need to be run before the PR can be merged. It should also ensure that website_docs are up to date and the contributor ran ./scripts/generate_website_docs.sh if they made changes to the source material

As seen in #5725, it is possible that components that have been completed already aren't wired up in the list of components. Currently, this seems to be the list of exporters and receivers that haven't been wired up yet:

$ ls -1 exporter/ > /tmp/exporters-available.txt
$ grep "github.com/open-telemetry/opentelemetry-collector-contrib" internal/components/components.go | sed 's/"//g

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

Currently (as of 0.7.0) NEOS tutorial that is opening up next to Cloud Shell window has 9 pages. 6 of them look similar but shorter versions of what's available in the user guide.
We want to shorten the NEOS tutorial and move details into the user guide. (Hugo static website under /website folder)

We'd like to add some documentation to the opentelemetry.io website.

the website_docs folder pushes all of its contents to https://opentelemetry.io/docs/php/

We should include our documentation in there in order to make it easier for end users to adopt our library.

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:

As part of #868 and #872 , currently we are embedding semantic convention attributes manually into C++ code. This can be automated.
This ticket is to check the feasibility of automatic generation of C++ code from semantic convention YAML data model using Jinja template engine.

Reference:
YAML data model for semantic conventions: https://github.com/open-telemetry/opentelemetry-specification

We have a facility to record events in the operator, like this:

https://github.com/open-telemetry/opentelemetry-operator/blob/7455eede6ae9347cf86cfc39cb2c90a6648ced0f/pkg/collector/reconcile/configmap.go#L179

But so far, we have been using the messages field in the status object, like this:

https://github.com/open-telemetry/opentelemetry-operator/blob/02dc4901d7ceefa630539374226665969f319

The current Getting Started guide includes a demo that use Zipkin, Jaeger and Prometheus. I am looking for a more simpler guide. Something that would show how to send a metric(s) using a utility like CURL and seeing the metric being recorded in a local file. This would help confirm that the installation of OTEL Collector is working normally.

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

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.