-
Notifications
You must be signed in to change notification settings - Fork 524
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
Map RUM PerformanceResourceTiming fields #9429
Conversation
This pull request does not have a backport label. Could you fix it @axw? 🙏
NOTE: |
Add field mappings for: - http.response.transfer_size - http.response.encoded_body_size - http.response.decoded_body_size The fields are mapped with `index: false`, to minimise storage overhead. They can still be used in searches, just a bit slower. The intake schema for these fields has been changed from float64 to int, as these are originally integer values. See https://w3c.github.io/resource-timing/#sec-performanceresourcetiming testdata, and hence approvals, have been updated to change the mock values from floats to integers.
📚 Go benchmark reportDiff with the
report generated with https://pkg.go.dev/golang.org/x/perf/cmd/benchstat |
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.
LGTM from the RUM agent side.
Regarding applying this change to other non-RUM agents, do we have (or plan to) do anything beyond updating the schema for now ? For example do we have to also attempt to capture similar attributes on HTTP spans ? |
@SylvainJuge no, there's no plans for that at the moment |
Confirmed that we can search and aggregate on In mapping:
|
Good catch @carsonip. AFAIK it's not currently used, so it doesn't matter at the moment. |
Package apm - 8.6.0-preview-1670294014 containing this change is available at https://epr.elastic.co/search?package=apm |
Motivation/summary
Add field mappings for:
The fields are mapped with
index: false
, to minimise storage overhead. They can still be used in searches, just a bit slower.The intake schema for these fields has been changed from float64 to int, as these are originally integer values.
See https://w3c.github.io/resource-timing/#sec-performanceresourcetiming
testdata, and hence approvals, have been updated to change the mock values from floats to integers.
Checklist
apmpackage
have been made)How to test these changes
Related issues
None