|
|
|
syntax = "proto3";
|
|
|
|
|
|
|
|
package envoy.config.metrics.v2;
|
|
|
|
|
|
|
|
import "envoy/api/v2/core/grpc_service.proto";
|
|
|
|
|
|
|
|
import "udpa/annotations/status.proto";
|
|
|
|
import "validate/validate.proto";
|
|
|
|
|
|
|
|
option java_package = "io.envoyproxy.envoy.config.metrics.v2";
|
|
|
|
option java_outer_classname = "MetricsServiceProto";
|
|
|
|
option java_multiple_files = true;
|
|
|
|
option (udpa.annotations.file_status).package_version_status = FROZEN;
|
|
|
|
|
api: protoxform tool and API reformat. (#8309)
This patch introduces a new tool, protoxform, that will be the basis of
the v2 -> v3 migration tooling. It operates as a Python protoc plugin,
within the same framework as protodoc, and provides the ability to
operate on protoc AST input and generate proto output.
As a first step, the tool is applied reflexively on v2, and functions as
a formatting tool. In later patches, this will be added to
check_format/fix_format scripts and CI.
Part of #8082.
Risk level: medium (it's possible that some inadvertent wire changes
occur, if they do, this patch should be rolled back).
Testing: manual inspection of diff, bazel test //test/..., some
grep/diff scripts to ensure we haven't lost any comments.
Signed-off-by: Harvey Tuch <htuch@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ 08b123a8321d359ea66cbbc0e2926545798dabd3
5 years ago
|
|
|
// [#protodoc-title: Metrics service]
|
|
|
|
|
|
|
|
// Metrics Service is configured as a built-in *envoy.stat_sinks.metrics_service* :ref:`StatsSink
|
|
|
|
// <envoy_api_msg_config.metrics.v2.StatsSink>`. This opaque configuration will be used to create
|
|
|
|
// Metrics Service.
|
|
|
|
// [#extension: envoy.stat_sinks.metrics_service]
|
|
|
|
message MetricsServiceConfig {
|
|
|
|
// The upstream gRPC cluster that hosts the metrics service.
|
api: protoxform tool and API reformat. (#8309)
This patch introduces a new tool, protoxform, that will be the basis of
the v2 -> v3 migration tooling. It operates as a Python protoc plugin,
within the same framework as protodoc, and provides the ability to
operate on protoc AST input and generate proto output.
As a first step, the tool is applied reflexively on v2, and functions as
a formatting tool. In later patches, this will be added to
check_format/fix_format scripts and CI.
Part of #8082.
Risk level: medium (it's possible that some inadvertent wire changes
occur, if they do, this patch should be rolled back).
Testing: manual inspection of diff, bazel test //test/..., some
grep/diff scripts to ensure we haven't lost any comments.
Signed-off-by: Harvey Tuch <htuch@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ 08b123a8321d359ea66cbbc0e2926545798dabd3
5 years ago
|
|
|
api.v2.core.GrpcService grpc_service = 1 [(validate.rules).message = {required: true}];
|
|
|
|
}
|