bryancall commented on issue #10948: URL: https://github.com/apache/trafficserver/issues/10948#issuecomment-4828155219
I am closing this as a support question rather than an Apache Traffic Server bug. The report describes per-"XML ID" bandwidth (summed across all XML IDs) coming out larger than the bandwidth measured at your network switch, gathered through the stats_over_http plugin on Apache Traffic Server 7.0.1. A couple of things to note. "XML ID" is Apache Traffic Control terminology (a Delivery Service XML ID), which is a separate project. Apache Traffic Server core has no per-XML-ID concept; the stats_over_http plugin only exposes global counters, so it cannot attribute bandwidth to an individual Delivery Service on its own. A sum of per-Delivery-Service numbers exceeding a single switch-port measurement is usually a measurement methodology question (double counting across edges, differing sampling windows, or units) rather than a defect in how Apache Traffic Server counts bytes, and the report does not include configuration, metric names, or a reproduction that points to an Apache Traffic Server counting bug. Apache Traffic Server 7.0.1 is also long past end of life. If you can still reproduce a specific, incorrect counter on a currently supported release with the exact metric names and steps, please open a new issue, or raise the Delivery Service accounting question with the Apache Traffic Control project. There has been no activity since the stale notice, so I am closing this out. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
