Find One Flutter Request on the Server

Find one Flutter request on the server.

That is basic full-stack debugging.

Flutter DevTools can show the app’s network call. The server still needs a way to find the same request in its own logs or traces.

Dust keeps that path explicit.

The Flutter HTTP client can send a header with the request. dust_server tracing can read the standard traceparent header. If it is valid, the server span joins the same trace. If it is missing, the server starts a new trace.

The response also carries traceparent.

So the flow stays simple:

• Flutter sends the API call;
• the generated client maps the header;
• the server records the request span;
• the response gives back the trace id.

Do not put secrets in trace data. Use ids that are safe to store.

Docs used: Flutter DevTools Network view, Dust HTTP header parameters, dust_server tracing, and dust_server middleware.

Dust #DustServer #HTTPClient #Flutter