You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@drill.apache.org by br...@apache.org on 2016/07/14 18:42:30 UTC
[2/2] drill git commit: update drill metrics wording this vs the
update drill metrics wording this vs the
Project: http://git-wip-us.apache.org/repos/asf/drill/repo
Commit: http://git-wip-us.apache.org/repos/asf/drill/commit/4bb3aa83
Tree: http://git-wip-us.apache.org/repos/asf/drill/tree/4bb3aa83
Diff: http://git-wip-us.apache.org/repos/asf/drill/diff/4bb3aa83
Branch: refs/heads/gh-pages
Commit: 4bb3aa839e16a50aa40d71ec8c39a010a1fc753d
Parents: 6d618be
Author: Bridget Bevens <bb...@maprtech.com>
Authored: Thu Jul 14 11:41:09 2016 -0700
Committer: Bridget Bevens <bb...@maprtech.com>
Committed: Thu Jul 14 11:41:09 2016 -0700
----------------------------------------------------------------------
.../070-monitoring-metrics.md | 84 ++++++++++----------
1 file changed, 42 insertions(+), 42 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/drill/blob/4bb3aa83/_docs/performance-tuning/070-monitoring-metrics.md
----------------------------------------------------------------------
diff --git a/_docs/performance-tuning/070-monitoring-metrics.md b/_docs/performance-tuning/070-monitoring-metrics.md
index 8d91750..d53113b 100644
--- a/_docs/performance-tuning/070-monitoring-metrics.md
+++ b/_docs/performance-tuning/070-monitoring-metrics.md
@@ -1,42 +1,42 @@
----
-title: "Monitoring Metrics"
-date:
-parent: "Performance Tuning"
----
-
-As of Drill 1.7, Drill uses JMX ([Java Management Extensions](https://docs.oracle.com/javase/tutorial/jmx/)) to monitor queries at runtime. JMX provides the architecture to dynamically manage and monitor applications. JMX collects Drill system-level metrics that you can access through the Metrics tab in the Drill Web Console or a remote JMX monitoring tool, such as JConsole or the VisualVM + MBeans plugin. The Web Console Metrics tab contains the collected metrics as tables, counters, histograms, and gauges via JMX.
-
-## Remote Monitoring
-You can enable the remote JMX Java feature to monitor a specific JVM from a remote location. You can enable remote JMX with or without authentication. See the [Java documentation](http://docs.oracle.com/javase/7/docs/technotes/guides/management/agent.html).
-
-In `$DRILL_HOME/conf/drill-env.sh`, use the `DRILLBIT_JAVA_OPTS` variable to pass the relevant parameters. For example, to add remote monitoring on port 8048 without authentication:
-
- export DRILLBIT_JAVA_OPTS=\u201d$DRILLBIT_JAVA_OPTS -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=8048\u201d
-
-## Disabling Drill Metrics
-JMX metric collection is enabled, by default. You can disable the metrics option if needed.
-
-In `$DRILL_HOME/conf/drill-env.sh`, set the `drill.metrics.jmx.enabled` option to false through the `DRILLBIT_JAVA_OPTS` variable. Add the variable in `drill-env.sh` if it does not exist:
-
- export DRILLBIT_JAVA_OPTS="$DRILLBIT_JAVA_OPTS -Ddrill.metrics.jmx.enabled=false"
-
-The following table lists the predefined Drill system-level metrics that you can view through a JMX monitoring tool or the Drill Web Console:
-
-| Metric | Description |
-|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| drill.queries.running | The number of queries running for which the Drillbit is the Foreman. |
-| drill.queries.completed | The number of queries completed, canceled, or failed for which the Drillbit was the Foreman. |
-| drill.fragments.running | The number of query fragments currently running in the Drillbit. |
-| drill.allocator.root.used | The amount of memory (in bytes) used by the internal memory allocator. |
-| drill.allocator.root.peak | The peak amount of memory (in bytes) used by the internal memory allocator. |
-| heap.used | The amount of heap memory (in bytes) used by the JVM. |
-| non-heap.used | The amount of non-heap memory (in bytes) used by the JVM. |
-| count | The number of live threads, including daemon and non-daemon threads. |
-| fd.usage | The ratio of used file descriptors to total file descriptors on *nix systems. |
-| direct.used | The amount of direct memory (in bytes) used by the JVM. This metric is useful for debugging Drill issues. |
-| runnable.count | The number of threads executing an action in the JVM. This metric is useful for debugging Drill issues. |
-| waiting.count | The number of threads waiting to execute. Typically, threads waiting on other threads to perform an action. This metric is useful for debugging Drill issues. |
-| blocked.count | The number of threads that are blocked because they are waiting on a monitor lock. This metric is useful for debugging Drill issues. |
-
-
-
+---
+title: "Monitoring Metrics"
+date: 2016-07-14 18:41:09 UTC
+parent: "Performance Tuning"
+---
+
+As of Drill 1.7, Drill uses JMX ([Java Management Extensions](https://docs.oracle.com/javase/tutorial/jmx/)) to monitor queries at runtime. JMX provides the architecture to dynamically manage and monitor applications. JMX collects Drill system-level metrics that you can access through the Metrics tab in the Drill Web Console or a remote JMX monitoring tool, such as JConsole or the VisualVM + MBeans plugin. The Web Console Metrics tab contains the collected metrics as tables, counters, histograms, and gauges via JMX.
+
+## Remote Monitoring
+You can enable the remote JMX Java feature to monitor a specific JVM from a remote location. You can enable remote JMX with or without authentication. See the [Java documentation](http://docs.oracle.com/javase/7/docs/technotes/guides/management/agent.html).
+
+In `$DRILL_HOME/conf/drill-env.sh`, use the `DRILLBIT_JAVA_OPTS` variable to pass the relevant parameters. For example, to add remote monitoring on port 8048 without authentication:
+
+ export DRILLBIT_JAVA_OPTS=\u201d$DRILLBIT_JAVA_OPTS -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=8048\u201d
+
+## Disabling Drill Metrics
+JMX metric collection is enabled, by default. You can disable the metrics option if needed.
+
+In `$DRILL_HOME/conf/drill-env.sh`, set the `drill.metrics.jmx.enabled` option to false through the `DRILLBIT_JAVA_OPTS` variable. Add the variable in `drill-env.sh` if it does not exist:
+
+ export DRILLBIT_JAVA_OPTS="$DRILLBIT_JAVA_OPTS -Ddrill.metrics.jmx.enabled=false"
+
+The following table lists the predefined Drill system-level metrics that you can view through a JMX monitoring tool or the Drill Web Console:
+
+| Metric | Description |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| drill.queries.running | The number of queries running for which this drillbit is the Foreman. |
+| drill.queries.completed | The number of queries completed, canceled, or failed for which this drillbit was the Foreman. |
+| drill.fragments.running | The number of query fragments currently running in the drillbit. |
+| drill.allocator.root.used | The amount of memory (in bytes) used by the internal memory allocator. |
+| drill.allocator.root.peak | The peak amount of memory (in bytes) used by the internal memory allocator. |
+| heap.used | The amount of heap memory (in bytes) used by the JVM. |
+| non-heap.used | The amount of non-heap memory (in bytes) used by the JVM. |
+| count | The number of live threads, including daemon and non-daemon threads. |
+| fd.usage | The ratio of used file descriptors to total file descriptors on *nix systems. |
+| direct.used | The amount of direct memory (in bytes) used by the JVM. This metric is useful for debugging Drill issues. |
+| runnable.count | The number of threads executing an action in the JVM. This metric is useful for debugging Drill issues. |
+| waiting.count | The number of threads waiting to execute. Typically, threads waiting on other threads to perform an action. This metric is useful for debugging Drill issues. |
+| blocked.count | The number of threads that are blocked because they are waiting on a monitor lock. This metric is useful for debugging Drill issues. |
+
+
+