-
Notifications
You must be signed in to change notification settings - Fork 36
Description
Based on these F5 articles
https://clouddocs.f5.com/api/icontrol-rest/APIRef_tm_net_cmetrics.html
https://my.f5.com/manage/s/article/K21077941
Does F5 AST support gathering net cmetrics?
If not could this be planned into future releases? Please help share a timeline.
Since the destination IP in cmetrics can represent VIP pool members, SNAT IPs (potentially shared by multiple VIPs), or upstream routers (next hops in the forwarding path), we would also like the capability to associate cmetrics data with VIPs—possibly by mapping destination IPs to VIPs. This would also reduce metric cardinality by labeling metrics with VIP instead of individual destination IP.
This feature would enable us to build historical trends showing the number of routes falling into different MTU ranges per VIP and understand fragmentation issues or MTU path instability.