Pool Member Availability and Pool Member Utilization Panels are blank for F5s using Partitions
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- observability
Research direction
Start by reproducing the Pools dashboard flow for an F5 using multiple partitions, then inspect the f5.* metrics at the listed localhost:9090/federate endpoint and review the attached collector logs. Trace why the Pool Member Availability and Pool Member Utilization panels receive no data for non-Common partitions. Done means both panels display data for partitioned F5s while Common Partition Only behavior remains working.
Written by the indexing model from the issue text.
Description
Describe the bug
On F5s that are using partitions, under pools the Pool Member Availability and Pool Member Utilization Panels are blank. They work fine for F5s using Common Partition Only
To Reproduce
Steps to reproduce the behavior:
- Goto Dashboard for Pools
- Select F5 using Multiple Partions
- Select a Pool
- See blank Panels at the bottom of the page
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Does not seem version dependant, Just common to F5s NOT using the Common Partition
Attachments
If the issue is in regards to missing data in dashboards, please also run the following from the installed host and attach the output:
curl 'localhost:9090/federate?match[]=%7B__name__%3D~"f5.%2A"%7D'
1:~# curl 'localhost:9090/federate?match[]=%7B__name__%3D~"f5.%2A"%7D'
curl: (7) Failed to connect to localhost port 9090 after 0 ms: Connection refused
Logs for the collector can be gathered with:
docker logs application-study-tool-otel-collector-1 --tail 1000
- Dominant language
- Python
- Stars
- 106
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 55/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 ·
All issues in f5devcentral/application-study-tool
Similar issues
-
docs pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
pydantic/pydantic-ai#9800 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
[Bug]: With --api-server-count > 1, gauges such as vllm:num_requests_running have no samples until the first requestPossibly taken @roy6n23 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
vllm-project/vllm#59988 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
pymc-devs/pymc-examples#897 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 91/100