fjy closed pull request #6175: update sigar link
URL: https://github.com/apache/incubator-druid/pull/6175
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/docs/content/configuration/index.md 
b/docs/content/configuration/index.md
index bd9455b9292..8f3b1bdb9b4 100644
--- a/docs/content/configuration/index.md
+++ b/docs/content/configuration/index.md
@@ -188,7 +188,7 @@ The following monitors are available:
 |Name|Description|
 |----|-----------|
 |`io.druid.client.cache.CacheMonitor`|Emits metrics (to logs) about the 
segment results cache for Historical and Broker nodes. Reports typical cache 
statistics include hits, misses, rates, and size (bytes and number of entries), 
as well as timeouts and and errors.|
-|`io.druid.java.util.metrics.SysMonitor`|This uses the [SIGAR 
library](http://www.hyperic.com/products/sigar) to report on various system 
activities and statuses.|
+|`io.druid.java.util.metrics.SysMonitor`|This uses the [SIGAR 
library](https://github.com/hyperic/sigar) to report on various system 
activities and statuses.|
 |`io.druid.server.metrics.HistoricalMetricsMonitor`|Reports statistics on 
Historical nodes.|
 |`io.druid.java.util.metrics.JvmMonitor`|Reports various JVM-related 
statistics.|
 |`io.druid.java.util.metrics.JvmCpuMonitor`|Reports statistics of CPU 
consumption by the JVM.|


 

----------------------------------------------------------------
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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to