Currently, the unique flow_id is correctly generated and recorded in Glean telemetry, but it is not being forwarded in requests to the MLPA backend. References: flow id is generated here, "https://searchfox.org/firefox-main/rev/974b0546f470bf87a34d636a03607d788ba9305f/toolkit/components/ml/MLTelemetry.sys.mjs#50" https://searchfox.org/firefox-main/source/toolkit/components/ml/content/backends/OpenAIPipeline.mjs
Bug 2009456 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Currently, the unique flow_id is correctly generated and recorded in Glean telemetry, but it is not being forwarded in requests to the MLPA backend. This prevents correlation between client-side user flows and backend logs. Generation : flow_id is initialized in MLTelemetry.sys.mjs: https://searchfox.org/firefox-main/rev/974b0546f470bf87a34d636a03607d788ba9305f/toolkit/components/ml/MLTelemetry.sys.mjs#50 Integration Point: The ID needs to be injected into the request headers in OpenAIPipeline.mjs: https://searchfox.org/firefox-main/source/toolkit/components/ml/content/backends/OpenAIPipeline.mjs