gRPC

🚀 Feature

Currently the protoc-gen-openapiv2 can output a JSON Swagger/OpenAPI v2 API definition file. It would be nice to have an option to produce a YAML version instead.

One main benefits of YAML over JSON is the support for comments. I originally came here with the intent to suggest a feature of generator plugin to add a Code generated by protoc-gen-openapiv2. DO NOT EDIT. header

When using type google.protobuf.Timestamp, BloomRPC maps this to an object, e.g.:

"create_time": {
  "seconds": "1562723637",
  "nanos": 928852400
}

However, the Google API Design Guide specifies that the string representation should be RFC 3339 format, e.g. "2014-07-30T10:43:17Z"

This JSON mapp

On contexts with many APIs and APIs calling other APIs in chains, having too many spans in the zipkin/jaeger dashboards may lead to a too complex usage of such dashboards and of not necessary big data volumes.

For Tyk's admin team, the steps representing the time spent in each Tyk middleware are much valuable.

But the upstream APIs teams just want to know the global time spent in Tyk interna

我需要

可我在hyperf中不知道该如何使用write

As we all know golang has give us the feature that convert proto to json with https://github.com/golang/protobuf/blob/master/jsonpb/encode.go ,and with encode.go ,we can define diffrent style like casesensitive , emit empty , json indent and so on , we can see [Customizing Protobuf JSON Serialization in Go](https://seb-nyberg.medi

So that we don't have to check if the instance is an HttpData or HttpHeaders(trailers) in the subscriber.
Currently, we only have HttpResponse.split().

Is your feature request related to a problem? Please describe.
The gateway-proxy pods produce a large number of Prometheus metrics. In a sizable cluster these metrics can overwhelm the Prometheus servers that scrape the metrics endpoint.

Envoy bootstrap configuration contains a stats_config block that can used to filter the metrics that are exposed to prometheus https://www.envoyproxy.i