mirror of
https://github.com/elastic/kibana.git
synced 2025-04-25 10:23:14 -04:00
e6e78ac6d8
Currently Kibana forwards `query_range_secs` and `query_offset_secs` to mark the selected time range when reporting TTFMP event. This format caused some challenges to identify `from`, `to` date offsets in visualizations. To simplify, the PR renames and sends the three fields explicitly: - `query_from_offset_secs` offset to `0` (now), with -ve for past and +ve for future dates - `query_to_offset_secs` offset to `0` (now), with -ve for past and +ve for future dates - `query_range_secs` same as previously sent _This approach is followed after a discussion, and based on the [gist](https://gist.github.com/andrewvc/1f04a57a336d768e4ec5ff2eff06ba54) excerpt:_ ``` Earliest date -> QueryFrom Newest date -> QueryTo Duration -> QueryRange ``` ### Indexing These fields then should be mapped in the EBT indexer to ingest in the top level of the document, eventually removing the need to create runtime fields in data views for visualizations. Also, runtime fields in data views should be updated to reflect this change. For backward compatibility, the runtime fields can cater both the old and new field names conditionally. ### Testing - Ensure that the TTFMP events are correctly reporting the date ranges. ### Example  |
||
|---|---|---|
| .. | ||
| adding_api_capacity_test.mdx | ||
| adding_custom_performance_metrics.mdx | ||
| adding_performance_journey.mdx | ||
| running_performance_journey_in_cloud.mdx | ||