-
Notifications
You must be signed in to change notification settings - Fork 526
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
Allow overriding service
information from context
.
#1901
Conversation
beater/test_approved_es_documents/TestPublishIntegrationTransactions.approved.json
Show resolved
Hide resolved
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.
does this mean events can remove service
and user
information from an event when those are set in the metadata? are there tests for that?
I added some tests showing that data from the For I tried to explain this here, but I'll probably have to rephrase as it doesn't seem to be clear enough: user:
service:
|
* Allow overriding `service` information from `context`. fixes elastic#1175
* Allow overriding `service` information from `context`. fixes elastic#1175
* Allow overriding `service` information from `context`. fixes elastic#1175
This is not backported to 6.x, right? |
@eyalkoren confirm, it is not backported. |
Users with agents that support that upgrading the APM server to 7.x may get their views and aggregations completely changed. Is this documented somewhere? |
No, you're right, this is missing a changelog entry. I think this should go into the APM wide release notes and also into the server release notes. There was kind of a it implicitly works situation though with 6.x I first need to check what really changes for the users when upgrading. |
fixes #1175