You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by ke...@apache.org on 2021/04/22 13:22:04 UTC
[skywalking-data-collect-protocol] 01/01: Add throughput field for
ServiceMeshMetric
This is an automated email from the ASF dual-hosted git repository.
kezhenxu94 pushed a commit to branch throughput
in repository https://gitbox.apache.org/repos/asf/skywalking-data-collect-protocol.git
commit 1cda5dd6e37faa9018a20dee0c53496f43e77984
Author: kezhenxu94 <ke...@apache.org>
AuthorDate: Thu Apr 22 21:21:41 2021 +0800
Add throughput field for ServiceMeshMetric
---
service-mesh-probe/service-mesh.proto | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/service-mesh-probe/service-mesh.proto b/service-mesh-probe/service-mesh.proto
index 5f09a06..002a2ec 100644
--- a/service-mesh-probe/service-mesh.proto
+++ b/service-mesh-probe/service-mesh.proto
@@ -56,6 +56,9 @@ message ServiceMeshMetric {
// The sidecar/proxy internal error code, the value bases on the implementation.
// The envoy internal error codes are listed here, https://www.envoyproxy.io/docs/envoy/latest/api-v2/data/accesslog/v2/accesslog.proto#data-accesslog-v2-responseflags
string internalErrorCode = 14;
+
+ // The throughput detail of the mesh metrics.
+ Throughput throughput = 15;
}
enum Protocol {
@@ -64,5 +67,12 @@ enum Protocol {
TCP = 2;
}
+message Throughput {
+ // The received data in bytes
+ int64 received = 1;
+ // The sent data in bytes
+ int64 sent = 2;
+}
+
message MeshProbeDownstream {
}