Current Behaviour

The flamegraph sorts the siblings in ascending order by frame's name.
The reference to code is here

Expected Behaviour

The siblings should appear in order of their start time.
This can be achieved according to library docs mentioned [here](https://github.com/spiermar/d3-fla

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.

We now have a manually triggered github action doc-update which publishes the documentation from this repo to opentelemetry.io website repo (creates a PR there).

It would be nice to automate triggering of doc-update action as part of release process.

We can currently only implement a Sampler by calling SamplingResult.create. For results without attributes, we do return singletons from this method so it doesn't have any real overhead. But it's somewhat annoying to have to call create with a parameter and not so intuitive - every time I do it I still ctrl-click through the method to confirm it's not creating a new object. The alternative of

An optional parameter has been added to resources in the spec: https://github.com/open-telemetry/opentelemetry-specification/pull/1692/files

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

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#1636 and open-telemetry/opentelemetry-specification#1612

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.

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

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.

per #268

ConfirmedChannel is currently not patched and not instrumented by the amqplib plugin.
We need to add support for that as well