gRPC

🐛 Bug Report

This comment sums up the issue:

grpc-ecosystem/grpc-gateway#2398 (review)

Basically, our code is riddled with things like:

 	JSONRegister: system.RegisterSystemServiceHandler,

We can possibly fix this by changing all of our declarations of *grpc.ClientConn to grpc.ClientConnInterface. However, the `grpc.ClientC

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

Before you submit this issue, you has been search all existed issues and search the documentation

• [] I've been search all existed issues
• [] I've been read all documentation

Describe your question

How should I use alicloud MNS?

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

The current exporter doesn't support OpenMetrics format. It's fairly simple and most of this is actually handled directly by the prometheus library itself via the TextFormat class. See: https://github.com/AngerM/ag_server/blob/main/base/src/main/kotlin/dev/angerm/ag_server/http/PrometheusHandler.kt
Which I based off of https://github.com/prometheus/client_java/blob/master/simpleclient_httpserver

Describe the bug
In glooee, the 18-settings.yaml file is generated incorrectly if extauthCustomYaml is provided

To Reproduce
Steps to reproduce the behavior:

cat <<EOF > values.yaml
global:
  extauthCustomYaml: true
  extensions:
    extAuth:
      extauthzServerRef:
        name: external-auth-server
        namespace: kube-gloo-system
      httpService:
        pat