This is an automated email from the ASF dual-hosted git repository.
wujimin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-docs.git
The following commit(s) were added to refs/heads/master by this push:
new 36373ff 1.fix metrics table format problem 2.fix latencyDistribution
configuration name
36373ff is described below
commit 36373ffa0b9cf4d401a861c27f1d983f7f6a5c2c
Author: wujimin <[email protected]>
AuthorDate: Fri Apr 19 09:55:57 2019 +0800
1.fix metrics table format problem
2.fix latencyDistribution configuration name
---
.../en_US/general-development/metrics.md | 50 ++++++++++++----------
java-chassis-reference/en_US/styles/website.css | 13 +++++-
.../zh_CN/general-development/metrics.md | 50 ++++++++++++----------
java-chassis-reference/zh_CN/styles/website.css | 11 ++++-
4 files changed, 75 insertions(+), 49 deletions(-)
diff --git a/java-chassis-reference/en_US/general-development/metrics.md
b/java-chassis-reference/en_US/general-development/metrics.md
index 65339f0..1d761c2 100755
--- a/java-chassis-reference/en_US/general-development/metrics.md
+++ b/java-chassis-reference/en_US/general-development/metrics.md
@@ -79,7 +79,7 @@
<th>Description</th>
</tr>
<tr>
- <td rowspan="8">servicecomb.vertx.endpoints</td>
+ <td rowspan="8">servicecomb<br>.vertx<br>.endpoints</td>
<td>type</td>
<td>client</td>
<td></td>
@@ -129,7 +129,7 @@
<th>Description</th>
</tr>
<tr>
- <td rowspan="8">servicecomb.vertx.endpoints</td>
+ <td rowspan="8">servicecomb<br>.vertx<br>.endpoints</td>
<td>type</td>
<td>server</td>
<td></td>
@@ -179,14 +179,14 @@
<th>Description</th>
</tr>
<tr>
- <td rowspan="11">servicecomb.invocation</td>
+ <td rowspan="11">servicecomb<br>.invocation</td>
<td>role</td>
<td>CONSUMER、PRODUCER、EDGE</td>
<td>Is the CONSUMER, PRODUCER or EDGE side statistics</td>
</tr>
<tr>
<td>operation</td>
- <td>${microserviceName}.${schemaId}.${operationName}</td>
+ <td>${microserviceName}<br>.${schemaId}<br>.${operationName}</td>
<td>Method name called</td>
</tr>
<tr>
@@ -196,7 +196,7 @@
</tr>
<tr>
<td>status</td>
- <td>http status code<td>
+ <td>http status code</td>
<td></td>
</tr>
<tr>
@@ -221,14 +221,14 @@
<th>Description</th>
</tr>
<tr>
- <td rowspan="19">servicecomb.invocation</td>
+ <td rowspan="19">servicecomb<br>.invocation</td>
<td>role</td>
<td>CONSUMER</td>
<td>Statistics on the CONSUMER side</td>
</tr>
<tr>
<td>operation</td>
- <td>${microserviceName}.${schemaId}.${operationName}</td>
+ <td>${microserviceName}<br>.${schemaId}<br>.${operationName}</td>
<td>Method name called</td>
</tr>
<tr>
@@ -238,7 +238,7 @@
</tr>
<tr>
<td>status</td>
- <td>http status code<td>
+ <td>http status code</td>
<td></td>
</tr>
<tr>
@@ -320,14 +320,14 @@
<th>Description</th>
</tr>
<tr>
- <td rowspan="17">servicecomb.invocation</td>
+ <td rowspan="17">servicecomb<br>.invocation</td>
<td>role</td>
<td>PRODUCER</td>
<td>Statistics on the PRODUCER side</td>
</tr>
<tr>
<td>operation</td>
- <td>${microserviceName}.${schemaId}.${operationName}</td>
+ <td>${microserviceName}<br>.${schemaId}<br>.${operationName}</td>
<td>Method name called</td>
</tr>
<tr>
@@ -337,7 +337,7 @@
</tr>
<tr>
<td>status</td>
- <td>http status code<td>
+ <td>http status code</td>
<td></td>
</tr>
<tr>
@@ -412,14 +412,14 @@
<th>Description</th>
</tr>
<tr>
- <td rowspan="23">servicecomb.invocation</td>
+ <td rowspan="23">servicecomb<br>.invocation</td>
<td>role</td>
<td>EDGE</td>
<td>EDGE statistics</td>
</tr>
<tr>
<td>operation</td>
- <td>${microserviceName}.${schemaId}.${operationName}</td>
+ <td>${microserviceName}<br>.${schemaId}<br>.${operationName}</td>
<td>Method name called</td>
</tr>
<tr>
@@ -429,7 +429,7 @@
</tr>
<tr>
<td>status</td>
- <td>http status code<td>
+ <td>http status code</td>
<td></td>
</tr>
<tr>
@@ -588,17 +588,21 @@ _Note: Please change the version field to the actual
version number; if the vers
### 2. Configuration instructions
+<div class="metrics-cfg">
+
| Configuration Item | Default | Meaning |
| :--- | :--- | :--- |
-| `servicecomb.metrics.window_time` | 60000 | Statistical period, in
milliseconds<br>TPS, delay, etc. Periodic data, updated once per cycle, the
value obtained in the cycle, actually the value of the previous cycle |
-| servicecomb.metrics.latencyDistribution | | The latency distribution
time period definition in milliseconds<br>for
example:0,1,10,100,1000<br>indicates that the following latency scopes are
defined: [0, 1),[1, 10),[10, 100),[100, 1000),[1000, ) |
-| servicecomb.metrics.Consumer.invocation.slow.enabled | false | Whether to
enable slow call detection on the Consumer side<br>Level 4 priority definitions
can be supported by adding the suffix .${service}.${schema}.${operation} |
-| servicecomb.metrics.Consumer.invocation.slow.msTime | 1000 | If the latency
exceeds the configured value, the log will be output immediately, and the time
consumption information of the stage called this time will be
recorded.<br>Level 4 priority definitions can be supported by adding the suffix
.${service}.${schema}.${operation} |
-| servicecomb.metrics.Provider.invocation.slow.enabled | false | Whether to
enable slow call detection on the Provider side<br>Level 4 priority definitions
can be supported by adding the suffix .${service}.${schema}.${operation} |
-| servicecomb.metrics.Provider.invocation.slow.msTime | 1000 | If the latency
exceeds the configured value, the log will be output immediately, and the time
consumption information of the stage called this time will be
recorded.<br>Level 4 priority definitions can be supported by adding the suffix
.${service}.${schema}.${operation} |
-| servicecomb.metrics.prometheus.address | 0.0.0.0:9696 | prometheus listen
address |
-| servicecomb.metrics.publisher.defaultLog.enabled | false | Whether to output
the default statistics log |
-| servicecomb.metrics.publisher.defaultLog.endpoints.client.detail.enabled |
false | Whether to output each client endpoint statistics log, because it is
related to the target ip:port number, there may be a lot of data, so the
default is not output|
+| servicecomb.metrics.window_time | 60000 | Statistical period, in
milliseconds<br>TPS, delay, etc. Periodic data, updated once per cycle, the
value obtained in the cycle, actually the value of the previous cycle |
+| servicecomb.metrics<br>.invocation.latencyDistribution | | The latency
distribution time period definition in milliseconds<br>for
example:0,1,10,100,1000<br>indicates that the following latency scopes are
defined: [0, 1),[1, 10),[10, 100),[100, 1000),[1000, ) |
+| servicecomb.metrics<br>.Consumer.invocation.slow.enabled | false | Whether
to enable slow call detection on the Consumer side<br>Level 4 priority
definitions can be supported by adding the suffix
.${service}.${schema}.${operation} |
+| servicecomb.metrics<br>.Consumer.invocation.slow.msTime | 1000 | If the
latency exceeds the configured value, the log will be output immediately, and
the time consumption information of the stage called this time will be
recorded.<br>Level 4 priority definitions can be supported by adding the suffix
.${service}.${schema}.${operation} |
+| servicecomb.metrics<br>.Provider.invocation.slow.enabled | false | Whether
to enable slow call detection on the Provider side<br>Level 4 priority
definitions can be supported by adding the suffix
.${service}.${schema}.${operation} |
+| servicecomb.metrics<br>.Provider.invocation.slow.msTime | 1000 | If the
latency exceeds the configured value, the log will be output immediately, and
the time consumption information of the stage called this time will be
recorded.<br>Level 4 priority definitions can be supported by adding the suffix
.${service}.${schema}.${operation} |
+| servicecomb.metrics<br>.prometheus.address | 0.0.0.0:9696 | prometheus
listen address |
+| servicecomb.metrics.publisher.defaultLog<br>.enabled | false | Whether to
output the default statistics log |
+| servicecomb.metrics.publisher.defaultLog<br>.endpoints.client.detail.enabled
| false | Whether to output each client endpoint statistics log, because it is
related to the target ip:port number, there may be a lot of data, so the
default is not output|
+
+</div>
### 3.慢调用检测
After slow call detection is enabled, if there is a slow call, the
corresponding log will be output immediately:
diff --git a/java-chassis-reference/en_US/styles/website.css
b/java-chassis-reference/en_US/styles/website.css
index 6d18bc3..be819b4 100644
--- a/java-chassis-reference/en_US/styles/website.css
+++ b/java-chassis-reference/en_US/styles/website.css
@@ -8,7 +8,16 @@ table {
overflow-x: auto;
}
-.metrics-table {
+.metrics-cfg table, .metrics-table {
border-width: 1px;
font-size: 8px;
-}
\ No newline at end of file
+ table-layout: auto;
+}
+
+.metrics-table th, .metrics-table td {
+ white-space: nowrap;
+}
+
+.metrics-table td:last-child{
+ white-space: normal;
+}
diff --git a/java-chassis-reference/zh_CN/general-development/metrics.md
b/java-chassis-reference/zh_CN/general-development/metrics.md
index 9bb675d..037e247 100644
--- a/java-chassis-reference/zh_CN/general-development/metrics.md
+++ b/java-chassis-reference/zh_CN/general-development/metrics.md
@@ -79,7 +79,7 @@
<th>含义</th>
</tr>
<tr>
- <td rowspan="8">servicecomb.vertx.endpoints</td>
+ <td rowspan="8">servicecomb<br>.vertx<br>.endpoints</td>
<td>type</td>
<td>client</td>
<td></td>
@@ -129,7 +129,7 @@
<th>含义</th>
</tr>
<tr>
- <td rowspan="8">servicecomb.vertx.endpoints</td>
+ <td rowspan="8">servicecomb<br>.vertx<br>.endpoints</td>
<td>type</td>
<td>server</td>
<td></td>
@@ -179,14 +179,14 @@
<th>含义</th>
</tr>
<tr>
- <td rowspan="11">servicecomb.invocation</td>
+ <td rowspan="11">servicecomb<br>.invocation</td>
<td>role</td>
<td>CONSUMER、PRODUCER、EDGE</td>
<td>是CONSUMER、PRODUCER还是EDGE端的统计</td>
</tr>
<tr>
<td>operation</td>
- <td>${microserviceName}.${schemaId}.${operationName}</td>
+ <td>${microserviceName}<br>.${schemaId}<br>.${operationName}</td>
<td>调用的方法名</td>
</tr>
<tr>
@@ -196,7 +196,7 @@
</tr>
<tr>
<td>status</td>
- <td>http status code<td>
+ <td>http status code</td>
<td></td>
</tr>
<tr>
@@ -221,14 +221,14 @@
<th>含义</th>
</tr>
<tr>
- <td rowspan="19">servicecomb.invocation</td>
+ <td rowspan="19">servicecomb<br>.invocation</td>
<td>role</td>
<td>CONSUMER</td>
<td>CONSUMER端的统计</td>
</tr>
<tr>
<td>operation</td>
- <td>${microserviceName}.${schemaId}.${operationName}</td>
+ <td>${microserviceName}<br>.${schemaId}<br>.${operationName}</td>
<td>调用的方法名</td>
</tr>
<tr>
@@ -238,7 +238,7 @@
</tr>
<tr>
<td>status</td>
- <td>http status code<td>
+ <td>http status code</td>
<td></td>
</tr>
<tr>
@@ -320,14 +320,14 @@
<th>含义</th>
</tr>
<tr>
- <td rowspan="17">servicecomb.invocation</td>
+ <td rowspan="17">servicecomb<br>.invocation</td>
<td>role</td>
<td>PRODUCER</td>
<td>PRODUCER端的统计</td>
</tr>
<tr>
<td>operation</td>
- <td>${microserviceName}.${schemaId}.${operationName}</td>
+ <td>${microserviceName}<br>.${schemaId}<br>.${operationName}</td>
<td>调用的方法名</td>
</tr>
<tr>
@@ -337,7 +337,7 @@
</tr>
<tr>
<td>status</td>
- <td>http status code<td>
+ <td>http status code</td>
<td></td>
</tr>
<tr>
@@ -412,14 +412,14 @@
<th>含义</th>
</tr>
<tr>
- <td rowspan="23">servicecomb.invocation</td>
+ <td rowspan="23">servicecomb<br>.invocation</td>
<td>role</td>
<td>EDGE</td>
<td>EDGE的统计</td>
</tr>
<tr>
<td>operation</td>
- <td>${microserviceName}.${schemaId}.${operationName}</td>
+ <td>${microserviceName}<br>.${schemaId}<br>.${operationName}</td>
<td>调用的方法名</td>
</tr>
<tr>
@@ -429,7 +429,7 @@
</tr>
<tr>
<td>status</td>
- <td>http status code<td>
+ <td>http status code</td>
<td></td>
</tr>
<tr>
@@ -585,17 +585,21 @@ _注：请将version字段修改为实际版本号；如果版本号已经在dep
### 2.配置说明
+<div class="metrics-cfg">
+
| 配置项 | 默认值 | 含义 |
| :--- | :--- | :--- |
-| `Servicecomb.metrics.window_time` | 60000 |
统计周期，单位为毫秒<br>TPS、时延等等周期性的数据，每周期更新一次，在周期内获取到的值，实际是上一周期的值 |
-| servicecomb.metrics.latencyDistribution | |
时延分布时间段定义，单位为毫秒<br>例如：0,1,10,100,1000<br>表示定义了下列时延段[0, 1),[1, 10),[10,
100),[100, 1000),[1000, ) |
-| servicecomb.metrics.Consumer.invocation.slow.enabled | false |
是否开启Consumer端的慢调用检测<br>通过增加后缀.${service}.${schema}.${operation}，可以支持4级优先级定义 |
-| servicecomb.metrics.Consumer.invocation.slow.msTime | 1000 |
时延超过配置值，则会立即输出日志，记录本次调用的stage耗时信息<br>通过增加后缀.${service}.${schema}.${operation}，可以支持4级优先级定义
|
-| servicecomb.metrics.Provider.invocation.slow.enabled | false |
是否开启Provide端的慢调用检测<br>通过增加后缀.${service}.${schema}.${operation}，可以支持4级优先级定义 |
-| servicecomb.metrics.Provider.invocation.slow.msTime | 1000 |
时延超过配置值，则会立即输出日志，记录本次调用的stage耗时信息<br>通过增加后缀.${service}.${schema}.${operation}，可以支持4级优先级定义
|
-| servicecomb.metrics.prometheus.address | 0.0.0.0:9696 | prometheus监听地址 |
-| servicecomb.metrics.publisher.defaultLog.enabled | false | 是否输出默认的统计日志 |
-| servicecomb.metrics.publisher.defaultLog.endpoints.client.detail.enabled |
false | 是否输出每一条client endpoint统计日志，因为跟目标的ip:port数有关，可能会有很多数据，所以默认不输出 |
+| servicecomb.metrics.window_time | 60000 |
统计周期，单位为毫秒<br>TPS、时延等等周期性的数据，每周期更新一次，在周期内获取到的值，实际是上一周期的值 |
+| servicecomb.metrics<br>.invocation.latencyDistribution | |
时延分布时间段定义，单位为毫秒<br>例如：0,1,10,100,1000<br>表示定义了下列时延段[0, 1),[1, 10),[10,
100),[100, 1000),[1000, ) |
+| servicecomb.metrics<br>.Consumer.invocation.slow.enabled | false |
是否开启Consumer端的慢调用检测<br>通过增加后缀.${service}.${schema}.${operation}，可以支持4级优先级定义 |
+| servicecomb.metrics<br>.Consumer.invocation.slow.msTime | 1000 |
时延超过配置值，则会立即输出日志，记录本次调用的stage耗时信息<br>通过增加后缀.${service}.${schema}.${operation}，可以支持4级优先级定义
|
+| servicecomb.metrics<br>.Provider.invocation.slow.enabled | false |
是否开启Provide端的慢调用检测<br>通过增加后缀.${service}.${schema}.${operation}，可以支持4级优先级定义 |
+| servicecomb.metrics<br>.Provider.invocation.slow.msTime | 1000 |
时延超过配置值，则会立即输出日志，记录本次调用的stage耗时信息<br>通过增加后缀.${service}.${schema}.${operation}，可以支持4级优先级定义
|
+| servicecomb.metrics<br>.prometheus.address | 0.0.0.0:9696 | prometheus监听地址 |
+| servicecomb.metrics.publisher.defaultLog<br>.enabled | false | 是否输出默认的统计日志 |
+| servicecomb.metrics.publisher.defaultLog<br>.endpoints.client.detail.enabled
| false | 是否输出每一条client endpoint统计日志，因为跟目标的ip:port数有关，可能会有很多数据，所以默认不输出 |
+
+</div>
### 3.慢调用检测
开启慢调用检测后，如果存在慢调用，则会立即输出相应日志：
diff --git a/java-chassis-reference/zh_CN/styles/website.css
b/java-chassis-reference/zh_CN/styles/website.css
index 6d18bc3..023a0ee 100644
--- a/java-chassis-reference/zh_CN/styles/website.css
+++ b/java-chassis-reference/zh_CN/styles/website.css
@@ -8,7 +8,16 @@ table {
overflow-x: auto;
}
-.metrics-table {
+.metrics-cfg table, .metrics-table {
border-width: 1px;
font-size: 8px;
+ table-layout: auto;
+}
+
+.metrics-table th, .metrics-table td {
+ white-space: nowrap;
+}
+
+.metrics-table td:last-child{
+ white-space: normal;
}
\ No newline at end of file
