When executing synthetic transactions on an application, business should be able to distinguish between synthetic and real user traffic so that all the reporting tools like Dynatrace/Adobe analytics etc. can only calculate their KPIs/metrics based on real user traffic.
Is there already a solution for this?
If not, I was thinking to just add custom headers in synthetic execution and create request attribute rule based on the header value for Dynatrace to differentiate between synthetic transactions on server level. and for Adobe and other tools to also consume the same header value, although for that it may require some code changes as well in the application itself to pass on this header value to all the downstream layers.
