GTM - Metric Timers

Hi Bobbybobby ,

You can run

tmsh show net cmetrics

Are you using Prometheus or docker images to export GTM metrics.
Could you please share your scenario for using GTM metrics.

Metric values are cached only when a session is active, only when requested, and only when the value is no longer considered useful (fresh). Consider these factors when viewing Metrics, especially when trending.

path-ttl
Specifies the number of seconds that the system considers path
data to be valid for name resolution and load balancing purposes.
The default value is 2400. Note that this option must be greater
than the paths-retry option and less than or equal to 2419200 (28
days).

inactive-paths-ttl
Specifies the number of seconds that a path remains in the cache
after its last access. Valid values are 60 - 31536000 (1 year).
The default value is 604800 (7 days).

metrics-caching
Specifies the interval (in seconds) at which the system dumps path
and other metrics data. Valid values are 0 through 604800. The
default value is 3600; 0 (zero) turns this feature off.

inactive-ldns-ttl
Specifies the number of seconds that an inactive LDNS remains in
the cache. Each time an LDNS makes a request, the clock starts
again. Valid values are 60 - 31536000 (1 year). The default value
is 2419200 (28 days).

Please refer to
https://clouddocs.f5.com/cli/tmsh-reference/v14/modules/gtm/gtm_global-settings_general.html

https://clouddocs.f5.com/cli/tmsh-reference/v15/modules/gtm/gtm_global-settings_metrics.html

https://support.f5.com/csp/article/K9629

https://support.f5.com/csp/article/K14938