You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2020/04/07 02:30:21 UTC

[GitHub] [trafficcontrol] ocket8888 commented on issue #4521: Multi-interface Servers blueprint

ocket8888 commented on issue #4521: Multi-interface Servers blueprint
URL: https://github.com/apache/trafficcontrol/pull/4521#issuecomment-610138270
 
 
   > Is there any impact to:
   > https://tp.domain.net/#!/cache-checks and the backing api endpoint - `GET /servercheck`
   > https://tp.domain.net/#!/cache-stats and the backing api endpoint - `GET /caches/stats`
   > And these api endpoints as well:
   > `GET /cdns/health`
   > `GET /cdns/{name}/health`
   > `GET /deliveryservices/{id}/health`
   
   - `/servercheck` - No. That endpoint does not interact with the Monitor at all.
   - `/caches/stats` - This _does_ pull some stats from the Monitor, but the specific ones for which it's looking should be totally unaffected, as they are in relation to the operation of ATS and not the machine's network interfaces.
   - `/cdns/health`/`/cdns/{{name}}/health` - The output of this is generated by tabulating which cache servers are "healthy". The determination of what "healthy" means will change, but not the ability to or structure of doing so. That is, the output value may change for a particular CDN may change for that endpoint, but the endpoint itself need not change.
   - `/deliveryservices/{{ID}}/health` - Same as the CDN-based route.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services