You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/01/05 23:27:58 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15802854#comment-15802854 ]
ASF GitHub Bot commented on TC-87:
----------------------------------
GitHub user elsloo opened a pull request:
https://github.com/apache/incubator-trafficcontrol/pull/163
[TC-87] Modify monitoring config API to populate profiles based on ty…
…pe instead of profile name.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/elsloo/incubator-trafficcontrol 2.0.x_fix_monitoring_config_api
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-trafficcontrol/pull/163.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #163
----
commit fe151b476d90b97a0e7a6e112599e83e27904ee1
Author: Jeff Elsloo <je...@cable.comcast.com>
Date: 2017-01-05T23:26:29Z
[TC-87] Modify monitoring config API to populate profiles based on type instead of profile name.
----
> 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
> 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)