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 2019/11/08 19:15:01 UTC
[GitHub] [trafficcontrol] awilliams commented on a change in pull request
#4100: Docs misc fixes
awilliams commented on a change in pull request #4100: Docs misc fixes
URL: https://github.com/apache/trafficcontrol/pull/4100#discussion_r344326702
##########
File path: docs/source/overview/traffic_monitor.rst
##########
@@ -33,12 +33,12 @@ Traffic Monitor polls all :term:`cache servers` configured with a status of ``RE
- Storage performance (e.g.: writes, reads, frags, directories, etc).
- System performance (e.g: load average, network interface throughput, etc).
-Many of the application-level statistics are available at the global or aggregate level, some at the :term:`Delivery Service` level. Traffic Monitor uses the system-level performance to determine the overall health of the :term:`cache server` by evaluating network throughput and load against values configured in :ref:`to-overview`. Traffic Monitor also uses throughput and transaction statistics at the :term:`Delivery Service` level to determine :term:`Delivery Service` health. If astats is unavailable due to a network-related issue or the system statistics have exceeded the configured thresholds, Traffic Monitor will mark the :term:`cache server` as unavailable. If the :term:`Delivery Service` statistics exceed the configured thresholds, the :term:`Delivery Service` is marked as unavailable, and :ref:`tr-overview` will start sending clients to the overflow destinations for that :term:`Delivery Service`, but the :term:`cache server` remains available to serve other content,
+Many of the application-level statistics are available at the global or aggregate level, some at the :term:`Delivery Service` level. Traffic Monitor uses the system-level performance to determine the overall health of the :term:`cache server` by evaluating network throughput and load against values configured in :ref:`to-overview`. Traffic Monitor also uses throughput and transaction statistics at the :term:`Delivery Service` level to determine :term:`Delivery Service` health. If astats is unavailable due to a network-related issue or the system statistics have exceeded the configured thresholds, Traffic Monitor will mark the :term:`cache server` as unavailable. If the :term:`Delivery Service` statistics exceed the configured thresholds, the :term:`Delivery Service` is marked as unavailable, and :ref:`tr-overview` will start sending clients to the overflow destinations for that :term:`Delivery Service`, but the :term:`cache server` remains available to serve other content.
Review comment:
Changed trailing comma to period.
```diff
-,
+.
```
----------------------------------------------------------------
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