Associate a request id header to the logs
complete
Thomas Heyenbrock
complete
We've moved the Custom Attributes feature into GA, it's now stable to use for everybody!
Thomas Heyenbrock
in progress
Hey folks 👋 we recently shipped a new feature called Custom Attributes that allow you to define HTTP headers that will be stored in our metrics database and made available in the Stellate dashboard. In particular, you could use this to store the values of the
x-request-id
header, and Stellate would then show them in the details view of individual requests.The feature is currently in Beta, you can find the documentation here: https://stellate.co/docs/platform/custom-attributes
Marko Locher
open
Actually, re-reading this request, I'm going to re-open this and ask for more feedback.
As I mentioned in my previous message, Stellate now includes a
gcdn-request-id
header on requests to your GraphQL backends.That same ID is also shown in the details view on Stellates Metrics dashboard.
Any other headers included on an incoming request to Stellate (e.g. a Cloudflare Ray ID, or a similar header) are included on requests to your backend. However, they aren't shown in the Metrics dashboard.
If you'd like those (external) headers to show up in the Metrics dashboard, please let us know.
If the
gcdn-request-id
header already solves your use case, please let us know as well. :)Marko Locher
complete
Requests from Stellate to your GraphQL backends now include a
gcdn-request-id
header with a unique ID. That ID is also shown on the metrics dashboard and allows for easier tracing of requests through various systems.Cyan Globe
This would be huge. Right now, the request id in Stellate is kind of meaningless as we have no way of correlating Stellate requests to origin requests.
We also return a header that describes how much complexity/tokens a given operation consumed, so it'd be nice if that could be surfaced as well.
Sandro Volpicella
Yes! This would be super useful for us as well. Stellate has a request ID to every request. It would be great if we could pass them down to the API to trace requests through the whole system