rob05c edited a comment on issue #3006: DS health protocol loophole URL: https://github.com/apache/trafficcontrol/issues/3006#issuecomment-437390857 >The per DS throttle limits are not part of astats I think They are, actually. So, Astats contains remap rules, for example: `"plugin.remap_stats.my-cache-name.my-ds-name.my-cdn-name.example.net.in_bytes": 1234567,` The Monitor reads that stat, and identifies the DS name (which is actually a remap rule, so because it's possible to create multiple remaps to the same FQDN in TO, the identification isn't theoretically perfect; but in practice, we just don't do that). The Monitor then sums the results from every cache, to create the DS Stats, which it both provides (for e.g. Traffic Stats, Grafana), and uses for thresholds. The full stats are available from the Monitor at `/publish/DsStats`. The DS availability is served at `/publish/CrStates`, which is used by the Router. That said, I don't know that we have anyone running a CDN, who allows tenants to put in caps, with the desire to stop serving traffic after a byte cap. So, it's not a well-tested feature.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
