Both Sentry and AWS (common error tracing and entry points for clusters) have HTTP trace headers for origin requests that allow better visibility in-between Formplayer and other in-cluster services.
Ideally, formplayer should pull a set headers for each request from the entry point request and ensure they are propogated downstream to all requests to HQ. It should be determined what requests within Formplayer these are propagated for and which aren't (in-cluster and out-of-cluster) but probably tied to when we use the session / cookie auth.
Both Sentry and AWS (common error tracing and entry points for clusters) have HTTP trace headers for origin requests that allow better visibility in-between Formplayer and other in-cluster services.
Ideally, formplayer should pull a set headers for each request from the entry point request and ensure they are propogated downstream to all requests to HQ. It should be determined what requests within Formplayer these are propagated for and which aren't (in-cluster and out-of-cluster) but probably tied to when we use the session / cookie auth.