10 Jan 2023 01:09 AM - last edited on 10 Mar 2023 02:50 AM by Michal_Gebacki
Dynatrace Managed allows using only a single HTTP proxy This proxy is used for outbound connections such as Mission Control or Problem notifications. In more complex environments, there are sometimes situations when you need to use different proxies for different purposes. For example one proxy for access to internet access, another proxy for some integrations, etc.
A simple solution for that is to deploy tinyproxy on the Managed nodes, configure the upstream rules and have the Managed use the tinyproxy for outbound communication.
upstream http 10.10.10.254:8080 ".acme.com" upstream http 192.168.254.254:8888 ".dynatrace.com"
This example uses different upstream proxies for communication to .acme.com and .dynatrace.com
Indeed that's great! Thank you Julius! I wonder if we shouldn't put it into official documentation...
If dealing with updating documentation around managed proxy, please also consider to add explanation aboout the new(?!) Exclude host part .....
it's already there:
Also, you can exclude hosts from using the proxy. This is useful, for example, when you have configured problem integrations via webhooks with software residing in the internal network. Use a wildcard (
*) at the beginning or at the end of each host entry to include all URLs within a defined host domain.
Once again did not read till the end
Anyhow I would give it a small header .....
All the best and stay safe