02 May 2023 02:32 PM - last edited on 29 Aug 2024 02:13 PM by GosiaMurawska
Hello,
I am monitoring .net service in fullstack mode via oneagent on host. This service convert and format data to post in Kafka topics and this is consumed by the other .net service but we have found that Dynatrace is adding extra header which is 'x-dynatrace' along with existing headers.
Question:
1. Can we prevent Dynatrace from adding 'x-dynatrace' and what's the impact?
2. When consumer reads the topic will they get this header as well along with others?
3. What will be the correct way to monitor this service?
Solved! Go to Solution.
02 May 2023 04:55 PM - edited 02 May 2023 05:05 PM
Hi,
I do not recommend you touching that header:
You can see all request headers here.
Best regards
12 Aug 2024 10:01 AM
I would also like to know if its actually possible. Sometimes the client may insist on it
12 Nov 2024 10:01 AM
Hello,
I just stumbled over your post now, because I have a similar problem, where we need to stop the H-Dynatrace header from being added for a specific request.
I think the best way to do this is to add the URL path you would like to exclude under the 'URL-based sampling' setting. You have to switch on the toggle for 'Ignore URLs with specific path and/or query parameters.
More about that solution here: https://docs.dynatrace.com/docs/shortlink/url-sampling
Another possibility is, to exclude the web request under 'Deep monitoring' -> 'Exclude specific incoming web request URLs'.
Here you can define URL paths that you would like to exclude from monitoring and alerting. I am not sure though, if this also prevents the x-dynatrace header from being set.
12 Nov 2024 10:24 AM
Thanks a lot for this. Let me try it out
14 Nov 2024 02:46 PM
Short update to this:
This doesn't work. URL-based sampling basically creates a new URL type with all the sampled requests being part of the domain and the exclusion rules just filter the requests out of the Dynatrace cluster, but do not prevent the x-dynatrace header from being placed.