This repository was archived by the owner on Nov 24, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 355
This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Add clarity to server stats displayed in TP #5708
Copy link
Copy link
Open
Labels
Traffic Opsrelated to Traffic Opsrelated to Traffic OpsTraffic Portal v1related to Traffic Portal version 1related to Traffic Portal version 1improvementThe functionality exists but it could be improved in some way.The functionality exists but it could be improved in some way.low difficultythe estimated level of effort to resolve this issue is lowthe estimated level of effort to resolve this issue is lowmedium impactimpacts a significant portion of a CDN, or has the potential to do soimpacts a significant portion of a CDN, or has the potential to do so
Description
I'm submitting a ...
- improvement request (usability, performance, tech debt, etc.)
Traffic Control components affected ...
- Traffic Portal
Current behavior:
^^ these numbers are populated from the api call:
GET api/3.1/servers?type=EDGE
therefore, the labels "online caches", "reported caches", etc are misleading.
New behavior:
Labels should be:
- Online Edge Caches
- Reported Edge Caches
- Offline Edge Caches
- Admin Down Edge Caches
Or an even better solution would be to aggregate the numbers for ALL caches (edges* and mids*) which would require either making a few calls like:
GET api/3.1/servers?type=EDGE
GET api/3.1/servers?type=MID
and summing the results or making an api change to support something like:
GET api/3.1/servers?type=CACHE
which pulls numbers for any server of type EDGE* or MID*
Minimal reproduction of the problem with instructions:
Launch TP. View the cache status in the top right of the TP dashboard.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Traffic Opsrelated to Traffic Opsrelated to Traffic OpsTraffic Portal v1related to Traffic Portal version 1related to Traffic Portal version 1improvementThe functionality exists but it could be improved in some way.The functionality exists but it could be improved in some way.low difficultythe estimated level of effort to resolve this issue is lowthe estimated level of effort to resolve this issue is lowmedium impactimpacts a significant portion of a CDN, or has the potential to do soimpacts a significant portion of a CDN, or has the potential to do so
