|
10 | 10 | weight: 104
|
11 | 11 | ---
|
12 | 12 |
|
13 |
| -InfluxData provides a Grafana operational dashboard that provide observability |
14 |
| -into the your {{< product-name >}} cluster. Use the operational dashboard to |
15 |
| -monitor your cluster. |
| 13 | +InfluxData provides a Grafana operational dashboard that provides observability |
| 14 | +into your {{< product-name >}} cluster. |
| 15 | +Use the operational dashboard to monitor your cluster. |
16 | 16 |
|
17 | 17 | {{% note %}}
|
18 | 18 | #### Not available for all clusters
|
@@ -40,7 +40,7 @@ If you do not have login credentials, [contact InfluxData support](https://suppo
|
40 | 40 |
|
41 | 41 | ## Dashboard sections and cells
|
42 | 42 |
|
43 |
| -The dashboard is divided into the following sections that visualize metrics |
| 43 | +The dashboard contains the following sections that visualize metrics |
44 | 44 | related to the health of components in your {{< product-name >}} cluster:
|
45 | 45 |
|
46 | 46 | - [Query Tier Cpu/Mem](#query-tier-cpumem)
|
@@ -156,7 +156,7 @@ to the [Object store](/influxdb/cloud-dedicated/reference/internals/storage-engi
|
156 | 156 |
|
157 | 157 | #### CPU Utilization Ingesters (k8s)
|
158 | 158 |
|
159 |
| -CPU Utilization of Ingester pods as reported by the Kubernetes container usage. |
| 159 | +CPU utilization of Ingester pods as reported by the Kubernetes container usage. |
160 | 160 | Usage is reported by the number of CPU cores used by pods, including
|
161 | 161 | fractional cores.
|
162 | 162 | The CPU limit is represented by the top line in the visualization.
|
@@ -284,7 +284,7 @@ _These do not represent the most recent logs._
|
284 | 284 | The **Compaction Tier Cpu/Mem** section displays the CPU and memory usage of
|
285 | 285 | Compactor pods as reported by Kubernetes.
|
286 | 286 | [Compactors](/influxdb/cloud-dedicated/reference/internals/storage-engine/#compactor)
|
287 |
| -process and compress parquet files in the |
| 287 | +process and compress Parquet files in the |
288 | 288 | [Object store](/influxdb/cloud-dedicated/reference/internals/storage-engine/#object-store)
|
289 | 289 | to continually optimize storage.
|
290 | 290 |
|
@@ -330,10 +330,10 @@ following levels:
|
330 | 330 |
|
331 | 331 | Parquet files store data partitioned by time and optionally tags
|
332 | 332 | _(see [Manage data partition](https://docs.influxdata.com/influxdb/cloud-dedicated/admin/custom-partitions/))_.
|
333 |
| -After four L0 files accumulate for a partition, they are are eligible for compaction. |
| 333 | +After four L0 files accumulate for a partition, they're eligible for compaction. |
334 | 334 | If the compactor is keeping up with the incoming write load, all compaction
|
335 |
| -events will have exactly four files. If the number of L0 files compacted begins to |
336 |
| -to increase, it indicates the compactor is not keeping up. |
| 335 | +events have exactly four files. |
| 336 | +An increase in the number of L0 files compacted indicates the compactor isn't keeping up. |
337 | 337 |
|
338 | 338 | This histogram helps to determine if the Compactor is starting compactions as
|
339 | 339 | soon as it can.
|
@@ -367,7 +367,7 @@ that the Catalog may be overloaded or unresponsive.
|
367 | 367 |
|
368 | 368 | #### Catalog Op Latency (P90)
|
369 | 369 |
|
370 |
| -The 90th percentile (P90) of query latency against the catalog service per operation. |
| 370 | +The 90th percentile (P90) query latency for each operation against the catalog service. |
371 | 371 | A high P90 value indicates that the Catalog may be overloaded.
|
372 | 372 |
|
373 | 373 | ---
|
|
0 commit comments