I remember this feature is planned or maybe in the pipeline already. What exactly is the issue? Headers starting with X- do not imply any action on the called party. Normally they must be ignored if the called service does not know them.
Hello @Julius_Loman ,
We are also facing the same issue with our application where x-headers are not able to excluded due to which some of the api calls got impacted and therefore we were forced to disable the oneagent on the host.
Do you know if this feature is already planned or implemented to exclude the x-dynatrace header at process or service level so that we can set the same.
No, I don't think this is possible on your own, only by disabling oneagent features. What issue does the added header raise in your environment?
Thanks for your response on this @Julius_Loman . We have an AXWAY api gateway in between which is transforming the headers to sent the request to backend services and due to this x-dyantrace header - api transformation resulting into error due to this application got impacted. We have also raised a case #253305 in order to check if some option can be done from the dynatrace end or RFE is needed to fix this issue as we cannot go with infra-only mode as we want to monitor the application as full stack.
@Parkash_jha Is the situation when some axway policies are calculating checksum based on http headers and as they differ between incoming and outgoing requests? We had such a situation with one customer already.