Jon Christiansen

We are migrating from Gateway with our code to support OAuth tokens, and for several of our environments we need to support multiple issuers. In Gateway, we were using this...

Running it in verbose mode result with: ``` flamegraph -o my_flamegraph.svg --pid 4756 --verbose command "xctrace" "record" "--template" "Time Profiler" "--target-stdout" "-" "--output" "cargo-flamegraph.trace" "--attach" "4756" Mutually exclusive options provided:...

I believe this should provide a solve for this issue, no? https://github.com/apollographql/router/pull/6887

@Cameronjmayfield -- At Indeed, with the above change released in [Router 2.2.0](https://github.com/apollographql/router/releases/tag/v2.2.0) addressed the similar problem we have in some of our non-PROD environments requiring a JWKS that is used/supports...

This is a fairly important metric that we need to be able monitor at this point where we have the context of the client and the operation name. Can we...

Indeed is anxiously awaiting for this support to be added to improve our pipelines and shift left bad config as much as possible. Based on the feedback, I believe there...

Indeed is very interested in this particular feature to remove sending the complete request payload to the coprocessor, to reduce CPU and latency for the additional serialization/deserialization, when the only...

@bnjjj - I dont think this would provide us the same insights. The graphql_error metric increments once per graphql error on a response. The request.duration metric only increment once per...