-
Notifications
You must be signed in to change notification settings - Fork 11.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trace View: Remove "deployment.environment" default traces 2 logs tag #74986
Trace View: Remove "deployment.environment" default traces 2 logs tag #74986
Conversation
Backend code coverage report for PR #74986 |
Frontend code coverage report for PR #74986
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll also need to remove it from the docs and settings tooltip. You can search for deployment.environment and see the following files:
docs/sources/datasources/jaeger/_index.md
docs/sources/datasources/zipkin/_index.md
docs/sources/datasources/tempo/_index.md
TraceToLogsSettings.tsx
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-74986-to-v10.1.x origin/v10.1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x bd452fe904abcfe07a0b6e4fc089ece22fc28bf7
# When the conflicts are resolved, stage and commit the changes
git add . && git cherry-pick --continue If you have the GitHub CLI installed: # Push the branch to GitHub:
git push --set-upstream origin backport-74986-to-v10.1.x
# Create the PR body template
PR_BODY=$(gh pr view 74986 --json body --template 'Backport bd452fe904abcfe07a0b6e4fc089ece22fc28bf7 from #74986{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title "[v10.1.x] Trace View: Remove \"deployment.environment\" default traces 2 logs tag" --body-file - --label "type/bug" --label "type/docs" --label "area/explore" --label "area/frontend" --label "add to changelog" --label "area/panel/traceview" --label "backport" --base v10.1.x --milestone 10.1.x --web Or, if you don't have the GitHub CLI installed (we recommend you install it!): # Push the branch to GitHub:
git push --set-upstream origin backport-74986-to-v10.1.x
# Create a pull request where the `base` branch is `v10.1.x` and the `compare`/`head` branch is `backport-74986-to-v10.1.x`.
# Remove the local backport branch
git switch main
git branch -D backport-74986-to-v10.1.x |
…grafana#74986) * Remove deployment.environment default tag * format * remove mentions from docs
…#74986) * Remove deployment.environment default tag * format * remove mentions from docs
deployment.environment
is an OTEL semantic attribute, but unlikeservice.name
orservice.namespace
it is not automatically converted to a Loki label by Loki exporter or Grafana Agent. Thus it's very unlikely to exists and queries with it will return no data. It shouldn't be a default tag.