You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "Jeremy Mitchell (JIRA)" <ji...@apache.org> on 2017/08/15 17:21:01 UTC

[jira] [Commented] (TC-522) "Online Caches" on TP Dashboard is confusing

    [ https://issues.apache.org/jira/browse/TC-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127567#comment-16127567 ] 

Jeremy Mitchell commented on TC-522:
------------------------------------

My intent with the top bar of the dashboard page of TP was to show the count of caches grouped by status or health. Not to display the statuses of "other servers" (TR, TM, TP, etc, etc....)

!dashboard-cache-statuses.png!

So rather than changing the label to "Online Servers" which will mix things, I'd rather remove "Online Caches" altogether from the dashboard OR filter the api respone so it really shows the count of servers where type=EDGE|MID and status=ONLINE (which as you said should always be zero....)

from my understanding from [~elsloo] the ONLINE status can be used to force caches online (no monitoring) but maybe like you said it should never be used for caches or used with caution so maybe having this count at the top is a good thing to ensure the number stays at zero...

... or if really, truly, caches should never be set to ONLINE, the api should be modified to prevent it.

> "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)