-
Notifications
You must be signed in to change notification settings - Fork 111
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
Add global labels to spans #153
Comments
The environment will be added to all spans as of 7.4: elastic/apm-server#2471 IMHO, it would be consistent to do the same for global labels. Does someone have objections in terms of disk usage? I don't expect that users would add lots and lots of global labels. And if they add them, they generally want to be able to filter by those labels. |
Personally, I'm all for consistency. The less differences between transactions and spans the better. |
Filtering spans by labels has come up in multiple user conversations. In most cases its users wanting to add just a couple of labels(at the most)to track specific end to end user actions. |
Based on the comments here and in today's meeting, it seems like there's agreement that this should be done. @graphaelli could you create an APM Server issue and put it in a milestone? |
When can I expect this change? In which release it will be updated? |
Issue created but milestone decision is still pending, feel free to follow the linked issue. |
This will go out in 7.6. |
Server support has been merged. If agents do not need a new API or anything, this issue can be closed. |
AFAIK, they do not. We can reopen if needed. |
Currently, global labels are only added to transactions, metrics, and errors. There are several requests for enabling global labels for spans too.
The latest one: https://discuss.elastic.co/t/labels-are-getting-added-to-only-transaction-event-not-to-span-event/201069/
Some other use cases:
department
) to a specific index. By doing that it's possible to set up different retention/ILM policies based on the global label.The text was updated successfully, but these errors were encountered: