Feature request: GTM metrics enrichment
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- observability-sre
Research direction
Start by tracing the existing GTM observability collection around the BIG-IP endpoints for wideip/a/stats and gtm/pool/a/.../members/stats. Compare the current GTM metrics with the requested WideIP and pool metrics, then identify how availability, query volume, and member hit counts are represented. Done means the requested metrics are exposed consistently with existing LTM metrics and covered by the project's relevant checks.
Written by the indexing model from the issue text.
Description
Hey guys, I've been exploring the AST for LTM, APM and GTM observability.
The LTM seems pretty good and it has almost everything needed for full monitoring. The GTM support however seems to be very light at this moment in time. I believe a few metrics would make a big difference for it:
WideIP
f5_gtm_wideip_queries: Statistics per WideIP of query volume would be great - qps ideally, but even a plaintotal_queriescounter would be good.f5_gtm_wideip_availability- WideIP availability (e.g. available, offline, etc).
Those metrics can be fetched from:
Pools
f5_gtm_pool_member_hit_count- basically how often each member gets handed out relative to the others (member 1 returned 100 times, member 2 returned 1000 times, that kind of thing).f5_gtm_pool_member_availability- This is already there for LTM pool members and it's one of the most important metrics for actually monitoring of the service.f5_gtm_pool_availability- Overall pool status (e.g. available, offline, etc).
Those metrics can be fetched from:
- https://{gtm_address}/mgmt/tm/gtm/pool/a/~{partition}~{pool_name}/members/stats
- https://{gtm_address}/mgmt/tm/gtm/pool/a/stats
Happy to provide more details if useful.
- Dominant language
- Python
- Stars
- 106
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from f5devcentral/application-study-tool
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 62/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
f5devcentral/application-study-tool#267 · 7 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
All issues in f5devcentral/application-study-tool
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100