Issue encountered with synthetic monitoring on private location [Dynatrace Managed]

[lost_sheep]

Hi all,

[Background]

We are using Dynatrace Managed and have provisioned an environment active gate meant for synthetic monitoring. We registered a private location with the environment active gate.

[Problem]

When running Synthetic Monitoring, the test cases kept showing "timed out". When we analysed the activegate logs, we traced it to a 401 unauthorised issue relating to "beacon_sending_error".

Does anyone experienced a similar issue with running a private location active gate on Dynatrace Managed?

[AntonPineiro · Accepted solution]

Hi,

It can be a firewall issue. You can find here useful resources.

Best regards

[lost_sheep]

Hi Anton,

Thanks for advice. We went through the page and we don't think this is due to firewall issue as we checked the logs and verified that we did to managed to call through.

It seems to be missing a tenant token in the header being sent when the environment activegate is calling localhost:9999.

Does anybody know if we need to configure the token as the documentation seems to imply is automatically assigned when setting up the environment activegate.

Thanks!