Overview

This guide explains how to configure alert thresholds for Synthetics resources in OpsRamp. It covers the four ways you can configure alerts (and when to use each), step‑by‑step instructions to set thresholds from the resource and template screens, short descriptions of every alert field, examples, and best practices to avoid noisy alerts.

Why Configure Thresholds?

Setting thresholds helps you:

• Detect issues early: Convert metric deviations into actionable warnings and critical alerts.
• Minimize alert noise: Use repeat counts and templates to reduce false positives and standardize alert behavior.
• Maintain control: Apply global defaults via templates and override them for specific resources when needed.

Understanding Configuration Scopes

There are four levels at which you can configure thresholds:

1. Component Level (Resource Component)

   • What: Set thresholds for a specific component (location) within a resource.
   • When to Use: When a component has unique performance characteristics requiring custom thresholds.
     
     

2. Resource Level

   • What: Apply thresholds to the entire Synthetics resource.
   • When to Use: When the whole resource needs different settings from the template defaults.
     
     

3. Template Component Level

   • What: Define default thresholds for specific components within a template.
   • When to Use: To ensure consistent component behavior across multiple resources using the same template.
     
     

4. Template Level (Global)

   • What: Set global defaults in a template, applicable across SP, partner, client, or resource levels.
   • When to Use: For organization-wide or customer-wide standardization of alert behavior.

Scope Precedence:
The most specific configuration takes priority:
Component > Resource > Template Component > Template (Global)

Configuring Alert Thresholds from a Resource & Component Levels

Step 1: Access the Synthetics Resource

1. If the Synthetics resource is not already created, refer to Synthetics Resource guide.
2. Navigate to:
   Infrastructure → Search → Resource Categories → Web Service → Synthetics.
3. Select and open the desired resource.

   

Step 2: Open Metric Configuration

1. On the Overview page, click the three-dot menu (…) in the top-right corner.
2. Click on View Templates to open the Metric Configuration page.

   

Step 3: Assign a Template (if needed)

1. If no template is assigned:
   • Go to Setup → Account → Monitoring → Templates.
   • Click Add to create a new template
   • Assign the template to the resource.
2. Return to the resource’s Assigned Templates and open Monitored Metrics.

Step 4: Edit Thresholds

1. In the Monitored Metrics tab:
   • Locate the metric you want to configure.
   • Click the edit (✎) icon next to it.

     

2. Set the following fields:
   • Alert: Enable to trigger alerts for this metric.
   • Warning Threshold & Repeat Count
   • Critical Threshold & Repeat Count

     

3. Click Save to apply changes.

Configuring Alert Thresholds from a Template Component Level

1. Navigate to Setup → Account → Monitoring → Templates.
2. Filter the scope (for example: Client, Partner, or Service Provider).
3. Select the Collector Type as Synthetics, then click Filter.

   

4. Click Template Action → View Details.

   

5. Click on Metrics → Relevant Component Thresholds.

   

6. Configure the Alert Condition and click Add Component Threshold to apply.
   Select the Alert checkbox to receive alerts.

   

Configuring Alert Thresholds from a Template Level

1. Navigate to Setup → Account → Monitoring → Templates.
2. Filter the scope (for example: Client, Partner, or Service Provider).
3. Select the Collector Type as Synthetics, then click Filter.
4. Click Template Action → View Details.

   

5. Click the three-dot action icon (⋮) and select View Details.

   

6. In the Assigned Metrics section, click the action icon and then View Details.

   

7. On the new page:
   • Select Alert on Breach of Threshold
   • Select Availability

8. Click Save to apply the configurations.
9. Click Save again to save the template.

Alert Field Descriptions

Examples

• Basic Configuration:
  • Warning: >= 10, Repeat: 1 → Triggers on first occurrence.
  • Critical: >= 20, Repeat: 1 → Triggers on first occurrence.
• Noise Reduction:
  • Warning: > 13, Repeat: 2 → Triggers after two consecutive breaches.
  • Critical: < 40, Repeat: 3 → Triggers after three consecutive breaches.

Best Practices

• Use templates to ensure consistency across resources.
• Apply repeat counts to reduce false positives. Start with 1 or 2 based on sampling frequency.
• Document exceptions when overriding templates at the resource/component level.
• Test changes in a staging environment before applying to production.
• Monitor alert volume post-implementation and adjust thresholds or repeat counts as needed.