Overview

Websites and internet services can be monitored from different geographical locations - both public and private.

Scenario:
You want to verify that web applications are up and running and detect any fluctuations in network traffic. To gain visibility and improve user experience and application performance, synthetic monitoring can be used.

Solution:
Use synthetic monitoring for 24/7 monitoring of services across all locations, receiving regular updates. The SCRIPT – HTTP Synthetic Transaction Monitor simulates possible customer actions on a website, monitoring each path or action at configured intervals, and sends alerts for any issues before they impact customers.

Monitoring Environment Locations

Using Synthetic monitoring, you can monitor internet services from public and private locations. Depending on the requirements, you can choose one of the following monitoring environments:

  • Public and Private Locations
  • Public locations
  • Private locations

Public and Private Locations

If the environment includes web applications in both private and public locations, do the following to start monitoring:

Step 1: Whitelist the IP Address

  • Ensure IP addresses are whitelisted to enable access to the added monitors from each location. Refer to the list of whitelisted IP addresses for public synthetic servers. Refer to the Whitelisted IP addresses of public synthetic servers.

Step 2: Implement an Instrumentation Strategy

  • Install the gateway (version 5.0.0 or above) to monitor any synthetic resources.

Step 3: Onboard Resources and Users

  • Set up your environment to discover and manage resources. Create an account to perform tasks for your organization. Refer to Account Management for detailed steps.

Step 4: Enable Resource Management Profiles

Use gateway version 5.0.0 or above to enable internet and intranet monitoring. Enable the Synthetics Agent via Setup > Resources > Management Profiles > View Management Profile. The “OpsRamp Synthetic Service Status” template will be automatically assigned to gateway devices linked with the gateway profile.

Step 5: Setup Synthetic Monitors

Assign a synthetic template to initiate synthetic monitoring. Set permissions for creating, editing, viewing, and deleting synthetic monitors. Verify role access to ensure you have the necessary permissions. Configuring synthetic monitors enhances security and stabilizes IT operations. For more details, refer to Creating synthetic monitors.

Monitoring from Private and Public Locations

Public Locations

Synthetics support monitoring is available from multiple locations (Asia, Europe, or North America) across the globe. Managing monitors from different locations infers receiving performance and availability information of the applications and internet services.

To set up your environment for monitoring from a public location:

Monitoring from Public Location

Private Locations

Enabling synthetic monitoring from private locations using gateway helps administrators/SREs to track the availability and performance of the internal monitors using the internal network. Administrators can use the same test capabilities to track the availability of the monitors from a public location.

Monitoring from Private Location

Configuring Proxy Settings for Gateway Collector and OpsRamp Cloud

If there are any proxy in Gateway Collector and OpsRamp Cloud, follow the below steps to configure the proxy:

  1. Navigate to the directory /opt/opsramp/webprobe/conf/.
  2. Open config.cfg.
  3. Locate the proxy section and enter the required details for the proxy server and proxy port according to your configuration.
  4. Save the changes.
  5. Restart the Synthetic Service using following command.
    systemctl restart webprobe