-
Today, CONTRIBUTING asks users to fill out yaml files for metrics and definitions, but doesn't describe the new attribute registry layout we're moving towards. We should update that with guidance on …
-
**Describe your environment**
Python 3.8.5
opentelemetry-distro[otlp]==0.44b.0
Gunicorn 22.0.0
**Steps to reproduce**
1. Run a Gunicorn Flask app as described in [the documentation](https://git…
-
### Problem Statement
The `semconvutil` package follows semantic conventions for span attributes set during a round-trip of a client-request.
Exposing the utility functions from `semconvutil` wo…
els0r updated
6 months ago
-
- [x] #3416 - #3474
- [x] #3256 - #3475
- [ ] #3468
- [ ] #3478
-
When referring to the version of this library, NPM-js states that its most recent is 0.53.0 however this github repository contains a version that looks much further ahead. I did see the transition fr…
-
Hi.
Updating to the latest semconv release produces this warning for queue workers for the latest version of the auto instrumentation for laravel.
```
PHP Warning: Illuminate\Queue\Worker::getN…
-
Currently if someone uses OTel or Jaeger, the "time spent by span type" will be empty: https://github.com/elastic/apm/issues/471. The reason behind this is that breakdown metrics are computed by agent…
-
I have a simple setup with one Lambda function that starts a Textract analysis of a document via StepFunctions.
The textract task in the StepFunction definition sends a notification on an SQS which t…
-
Currently if a user clicks on "Break down by" the list of all available fields is shown. For logs explorer in combination with ECS / semconv, we can be opinionated about which fields users likely want…
-
The [Merge](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/sdk.md#merge) section of the Resource SDK specification, describes how the `schemaURL` of two…