Handling Radar Agent Availability Issues

Email, Slack notifications or advanced webhooks may be used to monitor and/or notify on-premise Radar Agent outages. We recommend the following best practices for configuring alerts that will quickly let notify your team of any issues specific to your agents.

• Create a Radar Agent Monitoring Test
• View Radar Agent Monitoring Test Results
• Use Advanced Webhooks

Create a Radar Agent Monitoring Test

This method will promptly notify the appropriate parties responsible for managing your Radar Agent so that they can quickly address any issues as soon as they occur.

If you have multiple on-premise Radar Agents, repeat the following steps so that you create a separate monitoring test for each agent.

Follow these steps:

1. Create a new test in API Monitoring.
2. Name the test ("Monitoring Test for Remote Agent <remote agent name>", for example).
3. Open the Editor menu.
4. Expand the Test Settings section.
5. Open the Locations subsection.
6. Select the Radar Agent you wish to monitor by toggling its option to On.
7. Open the Email Notifications (or Integrations for Slack) subsection.
8. Check the box for each team member that should be notified.
9. Under Select the frequency of email notifications, select Notify only when a test run fails due to on-premises agent issues.
10. Open the Schedules menu.
11. Click + Add Schedule.
12. Schedule the test (for example, every 15 minutes) and click Save Schedule.

View Radar Agent Monitoring Test Results

If BlazeMeter is unable to communicate with your Radar agent, test results that attempt to use that agent will be marked as Remote Agent Expired. This status is indicated in orange in the Dashboard, Latest Test Results, and Test Result progress bars.

Example Dashboard

Example Test Results

img alt="expired results" src="../Resources/article_attachments/360014852258/private-locations-expired-results.png" />

Test runs that cannot be completed due to issues with remote agents (both on-premises and cloud agents) as well as system errors are not counted towards test metrics such as success ratio, average response time, and more. In the following example, a number of test runs have failed due to an expired remote agent, but this does not impact success rate.

Use Advanced Webhooks

You can also monitor the health of your remote agents by using advanced webhooks.

BlazeMeter's advanced webhooks supports an agent_expired parameter, which indicates the status of the agent for the test run:

• true indicates that the agent is expired
• null indicates that the agent is available, or if a default BlazeMeter API Monitoring location is used