topic Re: Conflicting Headers with Kuberntes and OneAgent in Container platforms

Conflicting Headers with Kuberntes and OneAgent

jerome_cizeron — Wed, 15 Dec 2021 14:17:44 GMT

We got some issue as DYNATRACE is using ETag hearder to store info which are conflicting with standart Cache managment. Is ther a way to define specific hearder to be use by Dynatrace as for example X-DT-MYHEADER hearder typ

Re: Conflicting Headers with Kuberntes and OneAgent

skrystosik — Fri, 27 Sep 2019 13:23:57 GMT

Are you sure that DT is using ETag? We have multiple kuberneties environments and we've never had conflict on such header parameter. If there is such in your example, you should open support ticket. Unfortunately users are not able to define custom header params.

Sebastian

Re: Conflicting Headers with Kuberntes and OneAgent

jerome_cizeron — Fri, 27 Sep 2019 14:06:00 GMT

For me, I get this information for dev team ETag is modified as followed

W/"d2d8037bd06cd0df9fc0aaa1cbb9bf38:dtagent101751909170927224xag:dtagent101751909170927224xag"

On which you can see dtagent, all add data block our caching efficiency.

Re: Conflicting Headers with Kuberntes and OneAgent

skrystosik — Fri, 27 Sep 2019 14:29:37 GMT

Open support ticket then.

Sebastian

Re: Conflicting Headers with Kuberntes and OneAgent

Julius_Loman — Fri, 27 Sep 2019 15:31:42 GMT

You can turn off the etag header usage in application configuration. Dynatrace adds it's value to etag to speed up changes in application configuration only. Unless you application configuration in Dynatrace changes,the value added is the same. Thus it won't break up things. I have only encountered problems when web request service sent empty Etag headers. That is however a bug of the monitored application.

Re: Conflicting Headers with Kuberntes and OneAgent

skrystosik — Fri, 27 Sep 2019 15:45:31 GMT

Ok you're right, there is such setting:

Sebastian

Re: Conflicting Headers with Kuberntes and OneAgent

Julius_Loman — Fri, 27 Sep 2019 15:50:08 GMT

We had an issue when application was sending Etag header with just a space character. Dynatrace added it's info and the request was cached but it should not be. The app should not pass the header without a proper value.

Re: Conflicting Headers with Kuberntes and OneAgent

nicolas_nguyen — Mon, 10 Jun 2024 18:42:45 GMT

We have the same issue here but the configuration spotted to solve the issue is not available anymore...

Re: Conflicting Headers with Kuberntes and OneAgent

Julius_Loman — Mon, 10 Jun 2024 19:50:55 GMT

@nicolas_nguyen it's still there:

Re: Conflicting Headers with Kuberntes and OneAgent

nicolas_nguyen — Mon, 10 Jun 2024 20:28:11 GMT

Is there a way to disable this setting a the tenant level ?

thanks

Re: Conflicting Headers with Kuberntes and OneAgent

Julius_Loman — Tue, 11 Jun 2024 06:39:07 GMT

@nicolas_nguyen No, at least not by the user. What exact issue are you facing? Unless the etag headers are implemented incorrectly on your application, this does not have any effect.