浏览代码

Review feedback (heading, typos)

* iff and therefor
* mention merge in heading
* add note about checking query inspector
David Kaltschmidt 7 年之前
父节点
当前提交
27e7a28b37
共有 1 个文件被更改,包括 5 次插入3 次删除
  1. 5 3
      docs/sources/features/panels/table_panel.md

+ 5 - 3
docs/sources/features/panels/table_panel.md

@@ -25,7 +25,7 @@ The table panel displays the results of a query specified in the **Metrics** tab
 The result being displayed depends on the datasource and the query, but generally there is one row per datapoint, with extra columns for associated keys and values, as well as one column for the numeric value of the datapoint.
 You can change the behavior in the section **Data to Table** below.
 
-### Multiple Queries per Table
+### Merge Multiple Queries per Table
 
 > Only available in Grafana v5.0+.
 
@@ -36,7 +36,7 @@ In this example usage and capacity are metrics that will have corresponding data
 In its simplest case, both queries return time-series data with a numeric value and a timestamp.
 If the timestamps are the same, datapoints will be matched and rendered on the same row.
 Some datasources return keys and values (labels, tags) associated with the datapoint.
-These are being matched as well iff they are present in both results and have the same value.
+These are being matched as well if they are present in both results and have the same value.
 The following datapoints will end up on the same row with one time column, two label columns ("host" and "job") and two value columns:
 
 ```
@@ -57,7 +57,9 @@ Datapoint for query B: {time: 1, host: "node-9", value: 4}
 ```
 
 You can still merge both of the above cases by changing the conflicting column's **Type** to **hidden** in the **Column Styles**.
-Note that if each datapoint of your query results have multiple value fields like max, min, mean, etc., they will likely have different values and therefor will not match and render on separate rows.
+
+Note that if each datapoint of your query results have multiple value fields like max, min, mean, etc., they will likely have different values and therefore will not match and render on separate rows.
+If you intend for rows to be merged but see them rendered on separate rows, check the query results in the **Query Inspector** for field values being identical across datapoints that should be merged into a row.
 
 ## Options overview