You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "Steve Malenfant (JIRA)" <ji...@apache.org> on 2017/08/16 18:58:00 UTC
[jira] [Updated] (TC-534) Traffic Router statistics are not
aggregated
[ https://issues.apache.org/jira/browse/TC-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Malenfant updated TC-534:
-------------------------------
Description:
Looks like some of the stats APIs related to Traffic Router don't return proper data when there is more than 1 instance of Traffic Router (or will return data for OFFLINE TR).
This would affect statistics for Traffic Portal as an example.
Looking at the code, it doesn't seem to cycle through all the request routers available to get statistics from a Delivery Service as an example.
Known affected APIs :
/api/1.2/deliveryservices/:id/routing.json
Few things to take in consideration
- Skip OFFLINE traffic routers (I believe it does skip them today)
- Skip unreachable traffic routers
- Need to aggregate data? Numbers from `/api/1.2/deliveryservices/:id/routing.json` seems to be percentages. Does it matter to get an average from all request routers?
Note: I don't have full knowledge of what was intended by this API.
was:
Looks like some of the stats APIs related to Traffic Router don't return proper data when there is more than 1 instance of Traffic Router (or will return data for OFFLINE TR).
This would affect statistics for Traffic Portal as an example.
Looking at the code, it doesn't seem to cycle through all the request routers available to get statistics from a Delivery Service as an example.
Known affected APIs :
/api/1.2/deliveryservices/:id/routing.json
Few things to take in consideration
- Skip OFFLINE traffic routers
- Skip unreachable traffic routers
- Need to aggregate data? Numbers from `/api/1.2/deliveryservices/:id/routing.json` seems to be percentages. Does it matter to get an average from all request routers?
Note: I don't have full knowledge of what was intended by this API.
> Traffic Router statistics are not aggregated
> --------------------------------------------
>
> Key: TC-534
> URL: https://issues.apache.org/jira/browse/TC-534
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops API
> Affects Versions: 2.1.0, 2.2.0
> Reporter: Steve Malenfant
>
> Looks like some of the stats APIs related to Traffic Router don't return proper data when there is more than 1 instance of Traffic Router (or will return data for OFFLINE TR).
> This would affect statistics for Traffic Portal as an example.
> Looking at the code, it doesn't seem to cycle through all the request routers available to get statistics from a Delivery Service as an example.
> Known affected APIs :
> /api/1.2/deliveryservices/:id/routing.json
> Few things to take in consideration
> - Skip OFFLINE traffic routers (I believe it does skip them today)
> - Skip unreachable traffic routers
> - Need to aggregate data? Numbers from `/api/1.2/deliveryservices/:id/routing.json` seems to be percentages. Does it matter to get an average from all request routers?
> Note: I don't have full knowledge of what was intended by this API.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)