open-telemetry/opentelemetry-go

AI Summary: This GitHub issue requests the implementation of four specific OpenTelemetry SDK observability metrics (`otel.sdk.exporter.metric_data_point.inflight`, `exported`, `otel.sdk.exporter.operation.duration`, and `otel.sdk.metric_reader.collection.duration`) within the `go.opentelemetry.io/otel/exporters/prometheus` package. Additionally, it requires documenting these new metrics in GoDoc, providing an example for the documentation style.

AI Summary: This GitHub issue requests the addition of three new OpenTelemetry SDK observability metrics (`inflight` data points, `exported` data points, and `operation.duration`) to the `otlpmetricgrpc` exporter in the `opentelemetry-go` project. The task also includes documenting these new metrics using GoDoc, with examples and references provided for guidance.

AI Summary: This GitHub issue requests the addition of standard OpenTelemetry SDK observability metrics (`otel.sdk.exporter.span.inflight`, `otel.sdk.exporter.span.exported`, `otel.sdk.exporter.operation.duration`) to the `otlptracegrpc` exporter in the OpenTelemetry Go SDK. The implementation should include GoDoc documentation for these new metrics, following a provided example, and adhere to project observability guidelines, with references to similar work.

AI Summary: This GitHub issue requests the addition of self-observability metrics to the experimental `stdoutlog` exporter in the OpenTelemetry Go SDK. Users must enable this feature by setting `OTEL_GO_X_OBSERVABILITY=true`, after which the exporter should report `otel.sdk.exporter.log.inflight`, `otel.sdk.exporter.log.exported`, and `otel.sdk.exporter.operation.duration` metrics using the global `MeterProvider`. The task also includes documenting these new metrics and the feature in GoDoc.

AI Summary: This issue requests the implementation of self-observability metrics for the experimental Logs SDK `BatchProcessor`. It involves adding `otel.sdk.processor.log.processed`, `otel.sdk.processor.log.queue.size`, and `otel.sdk.processor.log.queue.capacity` metrics, which are enabled by the `OTEL_GO_X_OBSERVABILITY` environment variable and use the global `MeterProvider`. Additionally, the new feature and its metrics need to be documented in GoDoc.

AI Summary: This GitHub issue requests the addition of self-observability metrics to the OpenTelemetry Go Logs SDK's `SimpleProcessor`. Specifically, it requires implementing the `otel.sdk.processor.log.processed` metric, which should be enabled by setting the `OTEL_GO_X_OBSERVABILITY` environment variable to `true` and use the global `MeterProvider`. The new feature and metric must also be documented in GoDoc.

AI Summary: This issue requests the implementation of self-observability metrics for the experimental `stdoutmetric` exporter in the OpenTelemetry Go SDK. It requires tracking `inflight` and `exported` metric data points, along with the `operation.duration` of export operations, using the global `MeterProvider` when an environment variable is set. Additionally, GoDoc documentation for this new feature is needed.

AI Summary: Investigate and resolve high mutex contention in the OpenTelemetry Go SDK's metric sum aggregation. This involves analyzing the `sum.Add(1)` function within the `sum.go` file, potentially optimizing the mutex usage (e.g., exploring alternatives like RWLocks or per-attribute mutexes), and verifying performance improvements with delta and cumulative metrics. Testing should involve simulating high-concurrency scenarios to reproduce the issue and measure the impact of any changes.

AI Summary: Implement self-observability metrics (otel.sdk.exporter.span.inflight, otel.sdk.exporter.span.exported, otel.sdk.exporter.operation.duration) for the stdouttrace exporter in the OpenTelemetry Go SDK. This requires enabling the feature via an environment variable, using the global MeterProvider, and documenting the new functionality in GoDoc. The task involves understanding existing OpenTelemetry conventions and Go SDK internals.

AI Summary: Implement self-observability metrics for the OpenTelemetry Go Logs SDK, specifically the `otel.sdk.log.created` metric. This involves enabling the feature via an environment variable, using the global `MeterProvider`, and documenting the new functionality in GoDoc. Reference implementations and semantic conventions are provided.

AI Summary: Implement self-observability metrics (`otel.sdk.span.live`, `otel.sdk.span.started`) for the OpenTelemetry Go trace SDK, enabled via the `OTEL_GO_X_SELF_OBSERVABILITY` environment variable. This involves using the global `MeterProvider` and documenting the feature in GoDoc, referencing existing examples and a prototype pull request.

AI Summary: Implement self-observability metrics (otel.sdk.processor.span.processed, otel.sdk.processor.span.queue.size, otel.sdk.processor.span.queue.capacity) for the OpenTelemetry Go SDK's BatchProcessor, enabled via the OTEL_GO_X_SELF_OBSERVABILITY environment variable. This requires using the global MeterProvider and documenting the new feature in GoDoc.

AI Summary: The task involves improving the OpenTelemetry Go SDK's log recording functionality by adding deduplication for key-value collections within log record bodies. This should be done recursively, without applying attribute limits, to address potential redundancy and ensure compliance with the OpenTelemetry specification. The solution requires modifying the `Record.SetBody` function in the `sdk/log/record.go` file, incorporating logic similar to that found in lines 428-432 of the referenced file.

AI Summary: Implement a `Clone` method for the `go.opentelemetry.io/otel/log.Record` struct, mirroring the existing implementation in `go.opentelemetry.io/otel/sdk/log.Record`. This involves creating a deep copy of the `Record` struct to ensure that modifications to the cloned record do not affect the original.