PHP looks like a less mature OpenTelemetry implementation, but it exists: https://github.com/open-telemetry/opentelemetry-php#installation

If possible, additional instrumentation tutorial for these popular frameworks would be helpful:

1. Zend Framework 3
2. WordPress
3. Silverstripe
4. [Symfony]

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

Is your feature request related to a problem? Please describe.
A lot of the configuration validate methods will return early stating a singular problem of the configuration, this can lead to a rather long feedback loop addressing issues within the configuration within complicated configurations.

Describe the solution you'd like
Each validate functions must validate all errors and only

Bug Report

The current OTLP exporter below flattens nested array in Span.Atttributes (Activity.Tags in .NET) into a list of key value pairs with the same key for all these kv pairs. For example, activity.SetTag('arraykey', new int [] {1, 2, 3} is converted to JSON like list {{'arraykey': 1}, {'arraykey': 2}, {'arraykey': 3}} in OTLP. This could cause problem if the OTLP listener would lik

While checking the consistency of the tests in the repository, the instruments Counter, Histogram, UpDownCounter, Gauge are tested and could see Async Counter (CounterObserver) and Async UpDownCounter (UpDownCounterObserver) are not tested. By following this documentation in

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

In https://github.com/open-telemetry/opentelemetry-collector-contrib/runs/4688228948?check_suite_focus=true

Lint fails with this

processor/transformprocessor/config_test.go: Expected no more than 3 groups, got 4
processor/transformprocessor/factory_test.go: Import groups are not in the proper order: ["Std" "Third party" "Third party"]
processor/transformprocessor/internal/traces/proce

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

At the moment there are a few tests marked as Unit tests, which are actually integration tests. They test side-effects of a class or do not provide isolation through mocks, stubs or test-doubles. They create false positives in code coverage because of code execution in the leaking into the Unit Tests' code coverage reports.

• Move "integration test like" tests from Unit Tests into the Integrat

full error message

Error from server (InternalError): error when creating "abc": Internal error occurred: failed calling webhook "mopentelemetrycollector.kb.io": failed to call webhook: Post "https://opentelemetry-operator-controller-manager-service.openshift-operators.svc:443/mutate-opentelemetry-io-v1alpha1-opentelemetrycollector?timeout=10s": dial tcp 10.131.0.154:9443: connect: connect

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)

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:

Apple comes with CFNetwork API to enable applications to interact with FTP and HTTP protocols to access Internet resources. This means it doesn't explicitly need to use curl as an HTTP client library.

otel-cpp is designed to plugin any external client library by extending abstract classes defined in the ext::http::client namespace.
And HttpClientFactory factory is responsible to pick up the co

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.