Monitoring script is working either one of the AG, but not in both

[vjayaku]

Hi All,

Any idea why some scripts working fine in either one of the Gateways but not in both(AG1 or AG2)?

[Peter_Youssef]

Hi @vjayaku 

Kindly elaborate more on what type of scripts you're referring to,  to enables us addressing the target concern.

BR, 

Peter

[vjayaku]

Hello Peter,

While doing On demand execution with Browser monitor with Synthetic AG1, and Synthetic AG2 locations,  

AG1 is getting failed with the result of "CONNECTION_TIMED_OUT" and AG2 is working fine.

So just would like know how the same script is failing in AG1 and working fine with AG2.

[Peter_Youssef]

Hi @vjayaku 

You have two options:

• Ensure the second Syn AG is capable of reaching the target URLs and Dynatrace cluster communications are stable.
• Modify the timeout for the AG itself to avoid such error.

BR,

Peter

[Peter_Youssef]

Hi @vjayaku 

PFA ref:

• https://docs.dynatrace.com/docs/shortlink/activegate-custom-installation-windows#connection-timeout
• https://docs.dynatrace.com/docs/shortlink/activegate-custom-installation-linux#connection-timeout

KR,

Peter

[Peter_Youssef]

Hi @vjayaku 

If you're referring to :

• AG Purposes : https://docs.dynatrace.com/docs/ingest-from/dynatrace-activegate#expand--diagram-of-activegate-funct...
• AG Groups: https://docs.dynatrace.com/docs/ingest-from/dynatrace-activegate/activegate-group

If you're seeking details on the Multi-environment AG, feel free to review https://docs.dynatrace.com/docs/shortlink/sgw-multiple-environments

In case you're asking about AG Capabilities: https://docs.dynatrace.com/docs/ingest-from/dynatrace-activegate/capabilities

Hoping it helps.

BR,

Peter

[Peter_Youssef]

Hi @vjayaku 

If you're seeking  the AGs that handle extensions either v1 or V2 it depends on what you're exactly target monitoring.

The assignment is done automatically if the AGs are in Group.

BR,

Peter