Hi Everyone ,
Can someone please guide me on -to see proxy chain in distributed trace, do we need to add any plugin or by default proxy details are shown?
Thanks
SB
Hi Everyone ,
Can someone please guide me on -to see proxy chain in distributed trace, do we need to add any plugin or by default proxy details are shown?
Thanks
SB
Hello.
Dynatrace will automatically detects proxy without any plugins from meta-data of requests. For example: if you have HAproxy on host or kube-proxy - you can see this information on ServiceFlow - it will be discovered automatically.
You also can find this information on Trace level (PurePath level) in Summary tab:
On graphics you can also see tips:
For more information and examples I recommend to check Dynatrace blog these great articles: link#1, link#2
Regards,
Alex Romanenkov
Further to what @Romanenkov_Al3x already explained, you could enhance the service flow views by adding a more descriptive name for each proxy by adding a custom device, instead of just seeing the IP addresses.
Weâve also taken it one step further for a customer by integrating it with the F5 BIG-IP plugin, so when one clicks on the name in the right-hand area of the screen, youâre taken to the custom device, where you can then click the âShow detailsâ button and youâll be taken to the F5 plugin metrics for that specific pool.
How did you do it for the F5 Plugin, have a customer that wantâs the same for datapower.
Pretty sure Iâve had this somewhere before, but not able to find anything in the docs.
Hi @Swati_Bhat
Itâs automatically discovered out of the box by Dynatrace, in case you need to define or customize proxy configurations
for OA deployments use: --set-proxy=172.1.1.128:8080
For AG proxy configuration, feel free to visit: AG Proxy configurations
Regards,
Hi @pahofmann I had to set up custom devices for each of the F5 virtual servers, based on the IPs I saw in the service flow. Once the custom device was configured, with the same IP and a hostname, it detected the proxy in the service flow by the name and not the âmeaninglessâ IP address. If you configured the custom device to link to the F5 virtual server too, one could do the drilldown from service flow to the actual F5 plugin data directly ![]()
The âURL of your deviceâ field is what I used to link directly to the F5 pluginâs details, specifically the F5 virtual serverâs details in this case.
I hope that helps - if you need more detail on how to set it up, Iâll have to see if I can do a write-up with steps and post it here.
Hi @Swati_Bhat
You have options to:
Or
Simply, you can decide as per the proposed suggestions and actual setup.
KR,
Peter.