Conflicting etag with Kubernetes Application and OneAgent

[nina123]

Our app seems to be getting our etag values replaced by the dtagent{hash} value but our original etag seems to be missing - this seems to have started after a springboot update. This is what replaced the ETag: ":dtagent10339260603164134f1aX". According to Configure automatic injection — Dynatrace Docs, the etag is not supposed to replaced but appended to if it is used in the response.

As a workaround - we created application rule that captures the url and disabled the "cache control headers"

This is the Etag after workaround in place:returns our etag and the dtagent: 

ETag: "d148d4ecf48c3c2cbd6e9858b6a67f05bb3b3905fe9c1b2abc0458fc8abd4962:dtagent10339260603164134f1aX"

[sujit_k_singh]

Hi @nina123 

You're right — per the docs, OneAgent should append its dtagent{hash} to the existing ETag, not replace it. The fact you're seeing :dtagent... with no original value before the colon indicates OneAgent isn't capturing the original ETag at injection time.

This likely started after your Spring Boot update because newer versions changed how/when the ETag header gets set in the response lifecycle.

Your workaround (disabling cache control headers in the app rule) is valid and the resulting ETag format confirms the append logic works when the original value is visible to OneAgent at the right time.

I'd recommend opening a support ticket with Dynatrace — include your OneAgent version and the Spring Boot versions (before/after upgrade). This looks like a compatibility issue.

Thanks,

Sujit

[lubrman]

Hi @nina123 
I'm currently working on the same issue with Dynatrace Support. In our case, disabling Cache Control Header Optimizations fixed the issue.And now we're waiting for further guidance from Support.

[lubrman]

Hi @nina123 
I just wanted to ask whether you started experiencing this issue after upgrading to Spring Boot 4.0.5?