diff --git a/content/platform/_index.md b/content/platform/_index.md index ca1755bae..5004fdd78 100644 --- a/content/platform/_index.md +++ b/content/platform/_index.md @@ -13,7 +13,7 @@ weight: 1 ## InfluxData 1.x -The **InfluxData 1.x platform** includes the following open source components ([TICK stack](#tick-stack-components)): +The **InfluxData 1.x platform** includes the following open source components ([TICK stack](#influxdata-1-x-tick-stack)): - [Telegraf](#telegraf): collect data - [InfluxDB](#influxdb): store data diff --git a/content/platform/monitoring/influxdata-platform/internal-vs-external.md b/content/platform/monitoring/influxdata-platform/internal-vs-external.md index 78920828f..496080bce 100644 --- a/content/platform/monitoring/influxdata-platform/internal-vs-external.md +++ b/content/platform/monitoring/influxdata-platform/internal-vs-external.md @@ -29,7 +29,7 @@ internal goroutine statistics, write statistics, series cardinality, and others, and stores them in the `_internal` database. _For the recommendation about `_internal` databases, see [Disable the `_internal` database in production clusters](#disable-the-internal-database-in-production-clusters) below._ -[Monitoring dashboards](/platform/monitoring/monitoring-dashboards) are available +[Monitoring dashboards](/platform/monitoring/influxdata-platform/monitoring-dashboards/) are available that visualize the default metrics provided in each of these databases. You can also [configure Kapacitor alerts](/{{< latest "kapacitor" >}}/working/alerts/) to monitor and alert on each of these metrics. diff --git a/content/platform/monitoring/influxdata-platform/tools/kapacitor-measurements.md b/content/platform/monitoring/influxdata-platform/tools/kapacitor-measurements.md index 1ddd4e5ff..0005ecd07 100644 --- a/content/platform/monitoring/influxdata-platform/tools/kapacitor-measurements.md +++ b/content/platform/monitoring/influxdata-platform/tools/kapacitor-measurements.md @@ -37,55 +37,55 @@ Kapacitor exposes the following measurements and fields through the `/kacapitor/v1/debug/vars` endpoint. - [kapacitor](#kapacitor) - - [num_enabled_tasks](#num_enabled_tasks) - - [num_subscriptions](#num_subscriptions) - - [num_tasks](#num_tasks) -- [kapacitor_edges](#kapacitor_edges) + - [num_enabled_tasks](#num-enabled-tasks) + - [num_subscriptions](#num-subscriptions) + - [num_tasks](#num-tasks) +- [kapacitor_edges](#kapacitor-edges) - [collected](#collected) - [emitted](#emitted) -- [kapacitor_ingress](#kapacitor_ingress) - - [points_received](#points_received) -- [kapacitor_load](#kapacitor_load) +- [kapacitor_ingress](#kapacitor-ingress) + - [points_received](#points-received) +- [kapacitor_load](#kapacitor-load) - [errors](#errors) -- [kapacitor_memstats](#kapacitor_memstats) - - [alloc_bytes](#alloc_bytes) - - [buck_hash_sys_bytes](#buck_hash_sys_bytes) +- [kapacitor_memstats](#kapacitor-memstats) + - [alloc_bytes](#alloc-bytes) + - [buck_hash_sys_bytes](#buck-hash-sys-bytes) - [frees](#frees) - - [gc_sys_bytes](#gc_sys_bytes) - - [gcc_pu_fraction](#gcc_pu_fraction) - - [heap_alloc_bytes](#heap_alloc_bytes) - - [heap_idle_bytes](#heap_idle_bytes) - - [heap_in_use_bytes](#heap_in_use_bytes) - - [heap_objects](#heap_objects) - - [heap_released_bytes](#heap_released_bytes) - - [heap_sys_bytes](#heap_sys_bytes) - - [last_gc_ns](#last_gc_ns) + - [gc_sys_bytes](#gc-sys-bytes) + - [gcc_pu_fraction](#gcc-pu-fraction) + - [heap_alloc_bytes](#heap-alloc-bytes) + - [heap_idle_bytes](#heap-idle-bytes) + - [heap_in_use_bytes](#heap-in-use-bytes) + - [heap_objects](#heap-objects) + - [heap_released_bytes](#heap-released-bytes) + - [heap_sys_bytes](#heap-sys-bytes) + - [last_gc_ns](#last-gc-ns) - [lookups](#lookups) - [mallocs](#mallocs) - - [mcache_in_use_bytes](#mcache_in_use_bytes) - - [mcache_sys_bytes](#mcache_sys_bytes) - - [mspan_in_use_bytes](#mspan_in_use_bytes) - - [mspan_sys_bytes](#mspan_sys_bytes) - - [next_gc_ns](#next_gc_ns) - - [num_gc](#num_gc) - - [other_sys_bytes](#other_sys_bytes) - - [pause_total_ns](#pause_total_ns) - - [stack_in_use_bytes](#stack_in_use_bytes) - - [stack_sys_bytes](#stack_sys_bytes) - - [sys_bytes](#sys_bytes) - - [total_alloc_bytes](#total_alloc_bytes) -- [kapacitor_nodes](#kapacitor_nodes) - - [alerts_inhibited](#alerts_inhibited) - - [alerts_triggered](#alerts_triggered) - - [avg_exec_time_ns](#avg_exec_time_ns) - - [crits_triggered](#crits_triggered) + - [mcache_in_use_bytes](#mcache-in-use-bytes) + - [mcache_sys_bytes](#mcache-sys-bytes) + - [mspan_in_use_bytes](#mspan-in-use-bytes) + - [mspan_sys_bytes](#mspan-sys-bytes) + - [next_gc_ns](#next-gc-ns) + - [num_gc](#num-gc) + - [other_sys_bytes](#other-sys-bytes) + - [pause_total_ns](#pause-total-ns) + - [stack_in_use_bytes](#stack-in-use-bytes) + - [stack_sys_bytes](#stack-sys-bytes) + - [sys_bytes](#sys-bytes) + - [total_alloc_bytes](#total-alloc-bytes) +- [kapacitor_nodes](#kapacitor-nodes) + - [alerts_inhibited](#alerts-inhibited) + - [alerts_triggered](#alerts-triggered) + - [avg_exec_time_ns](#avg-exec-time-ns) + - [crits_triggered](#crits-triggered) - [errors](#errors) - - [infos_triggered](#infos_triggered) - - [oks_triggered](#oks_triggered) - - [points_written](#points_written) - - [warns_triggered](#warns_triggered) - - [write_errors](#write_errors) -- [kapacitor_topics](#kapacitor_topics) + - [infos_triggered](#infos-triggered) + - [oks_triggered](#oks-triggered) + - [points_written](#points-written) + - [warns_triggered](#warns-triggered) + - [write_errors](#write-errors) +- [kapacitor_topics](#kapacitor-topics) - [collected](#collected) --- diff --git a/content/platform/monitoring/influxdata-platform/tools/measurements-internal.md b/content/platform/monitoring/influxdata-platform/tools/measurements-internal.md index 5635d4385..11163b847 100644 --- a/content/platform/monitoring/influxdata-platform/tools/measurements-internal.md +++ b/content/platform/monitoring/influxdata-platform/tools/measurements-internal.md @@ -77,7 +77,7 @@ to visualize InfluxDB `_internal` metrics. - [hh](#hh-enterprise-only) (Enterprise only) - [writeShardReq](#writeshardreq) - [writeShardReqPoints](#writeshardreqpoints) -- [hh_database](#hh-database) (Enterprise only) +- [hh_database](#hh-database-enterprise-only) (Enterprise only) - [bytesRead](#bytesread) - [bytesWritten](#byteswritten) - [queueBytes](#queuebytes) @@ -111,7 +111,7 @@ to visualize InfluxDB `_internal` metrics. - [promReadReq](#promreadreq) - [promWriteReq](#promwritereq) - [fluxQueryReq](#fluxqueryreq) - - [fluxQueryDurationNs](#fluxquerydurationns) + - [fluxQueryDurationNs](#fluxqueryreqdurationns) - [queryReq](#queryreq) - [queryReqDurationNs](#queryreqdurationns) - [queryRespBytes](#queryrespbytes) @@ -220,7 +220,7 @@ to visualize InfluxDB `_internal` metrics. - [numFiles](#numfiles) - [tsm1_wal](#tsm1-wal) - [currentSegmentDiskBytes](#currentsegmentdiskbytes) - - [oldSegmentsDiskBytes](#oldsegmentsdiskbytes) + - [oldSegmentDiskBytes](#oldsegmentdiskbytes) - [writeErr](#writeerr) - [writeOk](#writeok) - [write](#write) @@ -234,7 +234,7 @@ to visualize InfluxDB `_internal` metrics. - [writeDrop](#writedrop) - [writeError](#writeerror) - [writeOk](#writeok) - - [writePartial](#writePartial-enterprise-only) (Enterprise only) + - [writePartial](#writepartial-enterprise-only) (Enterprise only) - [writeTimeout](#writetimeout) {{% /truncate %}} diff --git a/content/platform/troubleshoot/disk-usage.md b/content/platform/troubleshoot/disk-usage.md index 65f92c1ba..a1c6a63ac 100644 --- a/content/platform/troubleshoot/disk-usage.md +++ b/content/platform/troubleshoot/disk-usage.md @@ -12,7 +12,7 @@ menu: It's very important that components of your TICK stack do not run out of disk. A machine with 100% disk usage will not function properly. -In a [monitoring dashboard](/platform/monitoring/monitoring-dashboards), high disk usage +In a [monitoring dashboard](/platform/monitoring/influxdata-platform/monitoring-dashboards/), high disk usage will appear in the **Disk Utilization %** metric and look similar to the following: ![High disk usage](/img/platform/troubleshooting-disk-usage.png) diff --git a/content/platform/troubleshoot/oom-loops.md b/content/platform/troubleshoot/oom-loops.md index a8f329d92..a16c6aea1 100644 --- a/content/platform/troubleshoot/oom-loops.md +++ b/content/platform/troubleshoot/oom-loops.md @@ -14,7 +14,7 @@ of memory until the operating system is forced to kill and restart the process. When the process is killed, memory allocated to the process is released, but after restarting, it continues to use more and more RAM until the cycle repeats. -In a [monitoring dashboard](/platform/monitoring/monitoring-dashboards), an OOM loop +In a [monitoring dashboard](/platform/monitoring/influxdata-platform/monitoring-dashboards/), an OOM loop will appear in the **Memory Usage %** metric and look similar to the following: ![OOM Loop](/img/platform/troubleshooting-oom-loop.png)