jaegertracing/jaeger

AI Summary: This GitHub issue requests a manual upgrade of the `github.com/elastic/go-elasticsearch/v9` dependency to version `v9.3.1`. An automated pull request for this upgrade previously failed due to breaking changes introduced in the new version, necessitating manual intervention to adapt the codebase.

AI Summary: The GitHub issue describes a problem where CI metric diffs show irrelevant changes due to transient labels, specifically the `topic` label in Kafka exporter metrics. These labels are generated randomly during CI runs, causing noise in the diffs. The goal is to suppress these transient labels to ensure only meaningful metric differences are reported.

AI Summary: This GitHub issue reports a bug in Jaeger where duplicate tag keys are created when a tag is set both via the `--collector.tags` CLI parameter for the agent and within the application's tracer code. The expected behavior is to have only one instance of the tag key, requiring a defined precedence rule (e.g., CLI tag overwrites tracer tag, or vice-versa) for tag merging.

AI Summary: The task requires addressing linter errors introduced by an automated Go linter upgrade in the Jaeger project. This involves reviewing and fixing the reported issues to ensure code compliance with the updated linting rules, allowing the upgrade pull request to be merged.

AI Summary: The task requires upgrading the Jaeger distributed tracing platform to utilize OpenTelemetry Collector version 1.37. This involves resolving breaking changes introduced in the new collector version that are causing automated pull request failures. The solution will likely involve modifying Jaeger's codebase to accommodate these changes.

AI Summary: Debug and fix a bug in Jaeger's Elasticsearch storage causing incorrect handling of collection-type attributes in spans. The issue manifests as spans failing to load properly in the UI due to a type mismatch in the stored data. The task involves analyzing the Elasticsearch data, identifying the root cause of the type mismatch (likely in the data serialization/deserialization process), and implementing a fix to ensure correct storage and retrieval of collection-type attributes.

AI Summary: The task is to update the Jaeger project's documentation (CONTRIBUTING.md) to explicitly state that GNU sed (gsed) is a required dependency for running `make test` on macOS, and provide instructions on how to install it using Homebrew (`brew install gnu-sed`). This will improve the onboarding experience for new contributors by eliminating a common source of build errors.

AI Summary: The task requires replacing outdated OpenTelemetry semantic conventions (semconv) references from the `go.opentelemetry.io/collector/semconv` package with the updated `go.opentelemetry.io/otel/semconv` package throughout the Jaeger codebase. This is necessary to upgrade to the latest OpenTelemetry version and resolve build failures. The update involves finding and replacing all instances of the deprecated package, ensuring compatibility with the new structure, and potentially refactoring code that uses indirect references to the semconv package.

AI Summary: The issue describes a problem with the Jaeger SPM (Service Performance Monitoring) example in the `jaeger/docker-compose/monitor/README.md` file. The provided `docker run` commands fail to connect to the OTel collector due to incorrect endpoint configuration in the `config-spm.yaml` file. The task involves fixing the endpoint configuration in `config-spm.yaml` to enable successful trace generation and potentially investigating why metrics aren't appearing on the metrics page, even after the trace issue is resolved.

AI Summary: The task is to update the Jaeger distributed tracing platform to support Elasticsearch version 9. This involves identifying and resolving compatibility issues between Jaeger and Elasticsearch v9, potentially requiring code modifications and testing to ensure functionality and stability.

AI Summary: Resolve linter issues preventing the auto-upgrade of the Jaeger project, as identified in pull request #7282. This involves fixing various code style and potential error issues flagged by the linter.

AI Summary: The task involves removing dead code from the Jaeger project's codebase. This requires identifying unused code using the `deadcode` tool, researching the history of each identified function or package to understand its purpose and removal context, and then safely deleting the unused code after validation with maintainers.

AI Summary: The provided text lacks sufficient detail to understand the specific requirement. The issue mentions a pull request (#7229) and a discussion referencing a requirement, but the requirement itself is not described. More context from the linked pull request and discussion is needed to determine the exact task.