Add flag or field to identify error sources

[biubiubiuboomboomboom]

Component(s)

router

Is your feature request related to a problem? Please describe.

hello, everyone. currently , there is no specific flag or field in cosmo router to identify error sources. therefore, whenever an error occurs , we need to spend time confirming whether the error originates from cosmo or the subgraph.

subgraph error propagation is good feature that can help us propagate subgraph errors ,but it can't help us identify error sources .

Describe the solution you'd like

add a specific flag or custom field on the error body of cosmo router which can help us identify which errors originate from cosmo .

Describe alternatives you've considered

No response

Additional context

No response

[github-actions[bot]]

WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible. The roadmap is driven by our customers and we have to prioritize issues that are important to them. You can influence the priority by becoming a customer. Please contact us here.

[SkArchon]

Hi There,

Have you tried using OTEL spans, for example with jaeger, newrelic, datadog, etc, to observe where the errors are originating from?

Docs: https://cosmo-docs.wundergraph.com/router/open-telemetry#tracing

Regards, Wundergraph Team

[biubiubiuboomboomboom]

yes , we are currently using it this way . but traces and logs are backend-only , meaning clients cannot directly access such information.

[chensunny]

Hi There,

Have you tried using OTEL spans, for example with jaeger, newrelic, datadog, etc, to observe where the errors are originating from?

Docs: https://cosmo-docs.wundergraph.com/router/open-telemetry#tracing

Regards, Wundergraph Team

No, the tracing is sampled, when the error happens, The client needs more information to judge which component error