You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "Jeff Elsloo (JIRA)" <ji...@apache.org> on 2017/01/06 20:46:58 UTC

[jira] [Closed] (TC-87) Monitoring API does not include profiles for all EDGE and MID types

     [ https://issues.apache.org/jira/browse/TC-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Elsloo closed TC-87.
-------------------------
    Assignee: Jeff Elsloo

> Monitoring API does not include profiles for all EDGE and MID types
> -------------------------------------------------------------------
>
>                 Key: TC-87
>                 URL: https://issues.apache.org/jira/browse/TC-87
>             Project: Traffic Control
>          Issue Type: Bug
>          Components: Traffic Ops API
>    Affects Versions: 1.8.0
>            Reporter: Jeff Elsloo
>            Assignee: Jeff Elsloo
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> The current monitoring config API relies on profile names rather than server types to populate the profiles. If a server is assigned to type {{EDGE_FOO}} and its profile name does not begin with {{EDGE}}, the health parameters will not appear in this section. This means that downstream consumers have no visibility into health thresholds for a host configured as such.
> This part of the configuration should rely on the the {{server->type}} as we do in the legacy API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)