ASM script monitors fail with "Consecutive Errors"

Products

• CA App Synthetic Monitor

Issue/Introduction

Monitoring  teams receive multiple incidents for ASM script monitors failing with "Consecutive Errors." Specific symptoms include:

• Metric Name: SuperDomain|...|ASM|App Synthetic Monitor Agent|Monitors|...:Consecutive Errors
• Status: "Customer Endpoints are not Reachable via ASM Monitors."
• The monitors work intermittently or fail only from specific public stations.
• Service and client certificates are verified as valid, but SSL handshakes may fail (e.g., Error 7019).
• Log may show Error 7001 Assertion failure

Environment

• App Synthetic Monitor (SaaS)
• JMeter script monitors using JMeter version 4.0 or lower.
• ASM Public Stations undergoing backend patching or upgrades.

Cause

ASM public stations are being updated/upgraded to address vulnerabilities and improve performance. These updated environments require JMeter scripts to be compatible with JMeter 5.0. Older scripts (specifically version 4.0) may fail.

Resolution

Migrating the script monitors to JMeter 5.0 resolves these errors. Follow these steps:

1. Enable JMeter 5.0 Agent:

   • Log in to the ASM UI.
   • Navigate to My Profile > Preferences.
   • Enable the checkbox: "Use the new JMeter 5 agent for all JMeter monitors."
   • Save the changes. This ensures the monitor uses the JMeter 5 agent on all public stations.

2. Update the JMX Script Version:

   • Method A (Recommended): Open the existing .jmx script in the JMeter 5.0 desktop application and Save the file. This automatically updates the header to version 5.0.
   • Method B (Manual): Open the .jmx file in a text editor and update the version attribute in the header to jmeter="5.0".
   • Upload the updated script back to the ASM monitor configuration.

3. Verification:

   • Re-enable the monitor.
   • Monitor the logs to ensure the script execution is successful across all locations.