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
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 @@
Description
-servicecomb.vertx.endpoints
+servicecomb.vertx.endpoints
type
client
@@ -129,7 +129,7 @@
Description
-servicecomb.vertx.endpoints
+servicecomb.vertx.endpoints
type
server
@@ -179,14 +179,14 @@
Description
-servicecomb.invocation
+servicecomb.invocation
role
CONSUMER、PRODUCER、EDGE
Is the CONSUMER, PRODUCER or EDGE side statistics
operation
-${microserviceName}.${schemaId}.${operationName}
+${microserviceName}.${schemaId}.${operationName}
Method name called
@@ -196,7 +196,7 @@
status
-http status code
+http status code
@@ -221,14 +221,14 @@
Description
-servicecomb.invocation
+servicecomb.invocation
role
CONSUMER
Statistics on the CONSUMER side
operation
-${microserviceName}.${schemaId}.${operationName}
+${microserviceName}.${schemaId}.${operationName}
Method name called
@@ -238,7 +238,7 @@
status
-http status code
+http status code
@@ -320,14 +320,14 @@
Description
-servicecomb.invocation
+servicecomb.invocation
role
PRODUCER
Statistics on the PRODUCER side
operation
-${microserviceName}.${schemaId}.${operationName}
+${microserviceName}.${schemaId}.${operationName}
Method name called
@@ -337,7 +337,7 @@
status
-http status code
+http status code
@@ -412,14 +412,14 @@
Description
-servicecomb.invocation
+servicecomb.invocation
role
EDGE
EDGE statistics
operation
-${microserviceName}.${schemaId}.${operationName}
+${microserviceName}.${schemaId}.${operationName}
Method name called
@@ -429,7 +429,7 @@
status
-http status code
+http status code
@@ -588,17 +588,21 @@ _Note: Please change the version field to the actual
version number; if the vers
### 2. Configuration instructions
+
+
| Configuration Item | Default | Meaning |
| :--- | :--- | :--- |
-| `servicecomb.metrics.window_time` | 6 | Statistical period, in
millisecondsTPS, 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 millisecondsfor
example:0,1,10,100,1000indicates 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 sideLevel 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.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 sideLevel 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.Level 4 priority definitions can be supported by adding the suffix
