You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition, it is quite likely that the main date format is too granular (for example as seen above, these are millisecond granularity, but that's not useful when looking at the test result, which should be to second granularity).
As there is no scaled date format that includes this level of precision, the suggestion is to use a combination of scaled date formats, P1DT + PT1S in those places.
Use PT1S or P1DT+PT1S (using the same logic as now, depending on how recent the test is) here:
Uptime Overview Monitor List > Collapsed summary
Uptime Overview Monitor List > Expanded view
Use P1DT+PT1S here:
Monitor History list
Use the standard Scaled date format on the Pings over time charts (x-axis)
On the Overview page
On the Monitor History page
The text was updated successfully, but these errors were encountered:
shahzad31 said: If user changes those, do we have to worry about if it's not there or do we need some fallback in case those formats are removed by user.
Although the standard Kibana date/time format is used in some places, there are a number of places it is not.
For example, when the standard Kibana format is defined as:
it is shown on the check details view screenshot:
However, not elsewhere:
In addition, it is quite likely that the main date format is too granular (for example as seen above, these are millisecond granularity, but that's not useful when looking at the test result, which should be to second granularity).
As there is no scaled date format that includes this level of precision, the suggestion is to use a combination of scaled date formats,
P1DT
+PT1S
in those places.PT1S
orP1DT+PT1S
(using the same logic as now, depending on how recent the test is) here:P1DT+PT1S
here:The text was updated successfully, but these errors were encountered: