topic HTTP Synthetic Monitor Showing 403 Error in Synthetic Monitoring

HTTP Synthetic Monitor Showing 403 Error

fadilck — Sat, 22 Feb 2025 14:47:02 GMT

Hi,

I am configuring an endpoint url for synthetic http monitoring. The URL is directly accessible from web, it is an index page for login to an application.

However, when i setup http monitor using private synthetic active gate, the synthetic monitor is showing 403 error. Please let us know, why this issue is occurring. The active gate server does not have any restriction in accessing the url. How can this issue be fixed. This is a simple get request.

Regards

Fadil

Re: HTTP Synthetic Monitor Showing 403 Error

AntonioSousa — Sun, 23 Feb 2025 09:33:11 GMT

@fadilck,

This has happened to me in the past, as the load-balancer/(server that was handling the requests was treating the requests differently. Check if it is validating:

Browser user-agents
IP addresses

Re: HTTP Synthetic Monitor Showing 403 Error

gopher — Mon, 24 Feb 2025 00:44:54 GMT

@fadilck , you might want to review your approach to avoid this issue.
generally speaking:
If you are accessing a public facing endpoint, you should use a 'public' synthetics AG.
If you are accessing an air gapped / internal endpoint, you should use a 'private' synthetics AG.

If you are trying to access the public address from the private AG, it will need to route internally from the AG to the external address, traversing your network. this includes, proxies, firewalls & anything else in between...

If you need to use the private Active Gate, then you will need to look at the following proxy section by dynatrace which is used by the VUC controller of the Synthetics module: Proxy for ActiveGate — Dynatrace Docs
you can set your proxy-non-proxy-hosts for your external address to allow internal routing to occur as per your environment configuration.

Hope this helps.