[
https://issues.apache.org/jira/browse/TC-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127576#comment-16127576
]
Jeremy Mitchell commented on TC-522:
------------------------------------
Also, "Offline Caches" is misleading because this is really a count of "Offline
Servers" so the API really needs to be filtered to only include type=EDGE|MID
> "Online Caches" on TP Dashboard is confusing
> --------------------------------------------
>
> Key: TC-522
> URL: https://issues.apache.org/jira/browse/TC-522
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Portal
> Affects Versions: 2.2.0
> Reporter: David Neuman
> Priority: Minor
> Attachments: dashboard-cache-statuses.png
>
>
> The dashboard page of traffic portal shows Reported Caches, Healthy Caches,
> Unhealthy Caches, Online Caches, Offline Caches, etc. This is nice to have
> and definitely useful but "online caches" is a little mis-leading. Under
> normal circumstances, caches shouldn't be in an online state. They should
> only be in Reported, Admin-Down, or Offline states. This is because if they
> are online, TM will not monitor them, but TR will route to them. If TR is
> routing to caches that are not being monitored, we could be routing to caches
> with issues.
> Usually support servers are the only servers that are in an online state.
> We should either change the wording on the portal to be "Online Servers" or
> remove the online caches stat all together. My vote is to change the wording.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
