Kibana: [APM] Respect default time range defined in Kibana Advanced Settings

Created on 8 Oct 2019  路  10Comments  路  Source: elastic/kibana

The timepicker will default to past 24 hours. This is currently not configurable.

From Customer Success:
"The customer wanted to config this as it was slow to load and three hours was a much more reasonable timeframe for them"

This should most likely be changed here:
https://github.com/elastic/kibana/blob/19476083789666cfb8c6d55abb30266077592030/x-pack/legacy/plugins/apm/public/context/UrlParamsContext/constants.ts#L10

APM UI should follow the Kibana default value. Additionally it should be possible to set a APM specific default.

Kibana advanced settings
The default value can be retrieved from timepicker:timeDefaults
image

Additionally the user's selection should be stored in locale storage

Question for platform:
Should each app store the user-selection in locale storage separately or do we want to have a centralized solution for this.

Related: https://github.com/elastic/kibana/issues/51953

apm platform enhancement v7.9.0

Most helpful comment

Hi, @sqren is there any timeline for this fix? With 24 hours APM dashboard, it takes a lot of time to load it.

All 10 comments

Pinging @elastic/apm-ui (Team:apm)

Another point around whether we should keep the selected time range in LocalStorage for improved per user experience. Letting the user pick up view from where they left off.

Hi, @sqren is there any timeline for this fix? With 24 hours APM dashboard, it takes a lot of time to load it.

Looking forward to fix.

+1

@cauemarcondes you already did this for the obs landing page, right? would it be trivial to do for APM as well?

+1

@cauemarcondes you already did this for the obs landing page, right? would it be trivial to do for APM as well?

@sqren yes I did it. Very simple, we should get these values from kibana settings:

  • UI_SETTINGS.TIMEPICKER_QUICK_RANGES
  • UI_SETTINGS.TIMEPICKER_REFRESH_INTERVAL_DEFAULTS
  • UI_SETTINGS.TIMEPICKER_TIME_DEFAULTS

Or since I've done it already for the Obs landing page, we could use the same component.

Or since I've done it already for the Obs landing page, we could use the same component.

Either sounds good - whatever is easiest :)
Do you think you can make this happen for 7.9?

Do you think you can make this happen for 7.9?

Sure. I will do it this week.

Was this page helpful?
0 / 5 - 0 ratings