remap legacy otlp for Tempo to avoid conflicts with ephemeral Docker's range #2340
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.
Why
The changes primarily address port conflict issues and improve the configuration of the observability stack, specifically for the
temposervice within a Docker Compose setup. Remapping the OTLP port intempofrom55680to14400avoids conflicts with Docker's ephemeral port range, ensuring smoother deployment and operations.What
framework/.changeset/v0.12.4.mdframework/observability/compose/docker-compose.yamltemposervice, changed the OTLP HTTP legacy port mapping from55680:55680to14400:55680. This modification resolves potential conflicts by moving away from a port within Docker's default ephemeral port range.