11 Jan 2018 03:54 AM - last edited on 01 Jul 2021 06:27 AM by MaciejNeumann
We have configured our Dynatrace Managed Cluster to use a proxy server to connect to Dynatrace Mission Control, and this works as desired. We are now trying to integrate Dynatrace Managed to our local Ticketing tool using WebHooks. Our ticketing tool is internal and as such, has a local IP address. When trying to integrate, it seems as though Dynatrace tries to use the proxy and this fails.
Is there any way of specifying that local IP addresses should be ignored?
Solved! Go to Solution.
After trying numerous options, I finally managed to get this to work. The following solution worked in my environment (OS = RHEL):
- Navigate to $DT_HOME/services
- Make a backup of the server.sh file
- Edit the server.sh file and add the following to the "export" section
- Save the file and recycle your Managed Environment
Is this still valid for recent Dynatrace Managed sprints? Is has no effect in any environment I've tried. And the cluster management console still does not have any option to specify proxy exceptions.
It seems a bit like this was a secret 'feature' of Managed. If you're still using it Amit C does it still work? It seems even Dynatrace support can't confirm if this would work!
Eddie, use the solution by Christoph below.
The problem with Chris's solution below is it applies to all the webhooks - I want to be able to config some of our webhooks to use the proxy and some not. Or am i misunderstanding and it is possible with Chris's solution?
This is not possible I think.
There are least two options I can think of in this case:
I am no longer using the above solution. I eventually went to our Security guys and asked them to redirect traffic to the specific IP address for the Webhook back internally. I havent had an issue since.
Here is the official solution from Dynatrace:
Forgot to mention that an update could overwrite this script and the settings are gone. One more reason to integrate it somehow.
Hi there, the following configuration of /opt/dynatrace-managed/server/conf/config.properties does the trick. It then disable the proxy for all WebHooks.
proxy-off = true
None of these solutions work acros upgrades. The upgrade process will remove all changes you made these files. This is the case for the solution mentioned by @Amit C and @Christoph K. Anyone found a method that would work consistently across upgrades?
We have found out that there is a new section in CMC under Home --> Settings --> Internet proxy page that you can exclude hosts from using the proxy.