-
Notifications
You must be signed in to change notification settings - Fork 25.4k
Update traces duration mappings with appropriate unit type #129418
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
Update traces duration mappings with appropriate unit type #129418
Conversation
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 require a plugin version bump?
I'm not sure, but at least for Kibana side, it has already what it needs. The |
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.
- I think it'll need a bump like https://github.com/elastic/elasticsearch/pull/125672/files#diff-3d1dc07446e033e300759471937a7fdd10b34d5285d60097e2e9d66e3a42d1a7R4 for it to work on upgrade
- Is there a specific reason why we're targeting 9.0.3? It is post-FF now. Is the coordinated UI work present in 9.0 as well?
I'll target the version 15 then?
Then I'll just remove that, leave it for the next version. |
Sure but remember to rebase from time to time. There's at least 2 more PRs competing for version 15 (although I think it is fine as long as the plugin version changes across upgrades if there exist any changes)
If you like it for 9.0.4, you may keep the PR open and only merge after 9.0.3 release |
Pinging @elastic/es-data-management (Team:Data Management) |
Hi @Bluefinger, I've created a changelog YAML for you. |
Rephrasing this: if you like this in 9.0.4, please keep the 9.0.3 label, keep the backport PR open and only merge it after 9.0.3 release. |
Thanks and yes, it would a good idea for this to go to 9.0.4 |
Oh wait, I thought we were past 9.0.3 FF. We are not. Let's try to get it into 9.0.3. Sorry for the confusion @Bluefinger |
💔 Backport failed
You can use sqren/backport to manually backport by running |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
* Add 9.0 to lazy rollover due to elastic/elasticsearch#129418 * Remove if condition in workflow since it's skipping scheduled for some reason
Tested as a part of 9.1 APM Server test plan elastic/apm-server#17263. With the old APM Server (before the changes). ![]() With the new APM Server (the changes included). ![]() |
This PR is a small change/update to the
span.duration.us
andtransaction.duration.us
mappings for APM traces, simply adding the meta attributesunit
to allow these to be correctly formatted as duration fields on Kibana side in Discover.These mappings have been tested locally to work with what has been implemented here: elastic/kibana#174973
Closes elastic/kibana#217886