Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Features

This section describes the features available in Paragon Automation Release 2.0.0.

Paragon Automation Installation

You can install Juniper® Paragon Automation, Release 2.0.0, using a VMware ESXi 8.0 server. Paragon Automation runs on a Kubernetes cluster of primary and worker nodes. To install Paragon Automation, download the OVA bundle (OVA and .nvram files) or an OVF bundle (OVF, .vmdk, and .nvram files) from the software download site, and use the files to deploy the node VMs from the VMware ESXi server. The Paragon Automation cluster can be installed in an air-gap environment.

  • Paragon Shell CLI—Paragon Automation provides a custom containerized MGD (cmgd) user shell, called Paragon Shell. You can use the Paragon Shell to deploy and configure the Paragon Automation cluster. The Paragon Shell CLI is installed and available after you create the VMs on the VMware ESXi server using the OVA or OVF bundles. You can use Paragon Shell to:

    • Deploy and upgrade the Paragon Automation cluster.

    • Backup, restore, and edit the cluster configuration.

    • Create and edit users.

    • Retrieve cluster information for troubleshooting.

    [See Paragon Shell Overview.]

  • Troubleshoot using Paragon Shell CLI—You can troubleshoot Paragon Automation cluster-related issues using Paragon Shell CLI commands. Run the following commands on any of the cluster nodes to view support and troubleshooting information.

    When you execute the following commands on any one of the cluster nodes, a series of commands are executed one after the other:

    • request support information—Displays an in-depth status report of your Paragon Automation cluster.

    • request paragon troubleshooting information—Displays troubleshooting information of various Paragon Automation services. This command also generates a .tar.gz file that you can share with Juniper's technical assistance team (JTAC) for further evaluation.

    [See Troubleshoot Using the Paragon Shell CLI Commands.]

  • Back up and restore—You can back up your current Paragon Automation network and application configuration and restore the configuration from a backed up file using Paragon Shell. When you run the backup command, all the configuration information stored in ArangoDB and PostgreSQL database systems are backed-up. You can back up the configuration information while the microservices are running. The back up process does not affect the network operation. To back up the Paragon Automation configuration, use the request paragon backup start command.

    When you restore from a backed up configuration file, all microservices and applications are stopped and the cluster is not functional until the databases are restored. After the databases are restored to the backed-up configuration, the applications are brought back online and the restored configuration data is reparsed. To restore from a specific backup file, use the request paragon restore backup-id command.

    [See Back Up and Restore Paragon Automation.]

For more information on Paragon Automation installation, see Paragon Automation Installation and Upgrade Guide.

Device Life-Cycle Management

Device life-cycle management (LCM) encompasses the entire life-cycle of the device, from installing the device on-site, bringing the device under management, monitoring the device when it is in production, and finally decommissioning the device.

  • Plan to onboard, install, and onboard a device—Paragon Automation enables you to onboard a device as follows:

    Note:

    Before you start planning for device onboarding, ensure that you have created a resource profile by using REST APIs. Resource profiles help in automatic configuration of resources such as IPv4 loopback addresses and interface IPv4 addresses.

    • Plan for device onboarding—A Super User or Network Admin can plan for device onboarding by creating an onboarding plan. An onboarding plan contains device profiles and interface profiles, and Paragon Active Assurance configurations.

      A device profile contains device-level configurations, such as IPv4 loopback address, autonomous system (AS) number and routing protocols (BGP groups, path computation element protocol (PCEP), traffic engineering, and segment routing).

      You can also configure whether you want to run compliance scans to determine the authenticity of the device while the device is being onboarded and test connectivity to the edge devices, Internet endpoints, and cloud provider endpoints.

      An interface profile contains interface configurations such as IP addresses and protocols (OSPF, IS-IS, LDP, and RSVP).

      An onboarding plan includes one or more devices that may or may not be associated with one or more device and interface profiles.

      The configurations in the device and interface profiles are committed on the device during device onboarding. If needed, configurations are also committed after the device is onboarded. For example, if the plan has an RSVP LSP configured from a device to all the provider edge (PE) devices, an LSP is configured from the device to all the PE devices that are currently present in the network and also, to any PE device that might be added to the network after the device is onboarded.

      In addition, an onboarding plan contains instructions for a field technician to install pluggables, connect cables, and connect the device with neighboring devices.

      [See Network Implementation Plan Overview.]

    • Install and onboard the device—A device can be installed and onboarded by:

      • A field technician who can install the device and onboard it by using the guidance from the network implementation plan for the device.

      • After a device is installed at the site, a network administrator can onboard the device by copying the outbound SSH commands provided by Paragon Automation.

        If a network implementation plan exists for the device being onboarded, all the configurations in the plan are committed and integrity, health, and Active Assurance tests are executed on the device after the device is onboarded.

      [See Adopt a Device.]

    • Move device to production—You can view and monitor the progress of device onboarding from the Put Devices into Service page (Inventory > Device Onboarding > Onboarding Dashboard) or Troubleshooting Devices page (Observability > Troubleshooting Devices) of the Paragon Automation UI). After the onboarding tests are successful, you can move the device to production, configure services and continue monitoring the health and performance of the device.

      [See View Results of Automated Device Tests.]

  • Verify health and connectivity of a device—During and after a device is onboarded, Paragon Automation automatically performs a series of tests to verify the integrity, health, and connectivity of the device. You can monitor the result of the test in the following accordions that are displayed on the Paragon Automation GUI:

    Paragon Automation displays the following data after the checks:

    • Identity and location: Paragon Automation runs trust scan to determine the authenticity of the device. You can view the score from the trust scan along with other general details of the device (such as vendor, hostname, serial number) and the location of the site where the device is installed.

    • Remote management: You can view details on the management connection between the device and Paragon Automation. You can view the latest date and time when the device established or terminated outbound SSH and gNMI session and the status of the sessions, the date and time when the latest system log message and alarm were received by Paragon Automation, details about the system log and alarm, and details about the status of the synchronization between the device clock and the Network Time Protocol (NTP) server.

    • Hardware: Paragon Automation executes tests to determine the health and functioning of the device hardware. You can view the data about the number of healthy and unhealthy hardware components (PSUs, fans, line cards, CPU, and memory); the KPIs for the components; details about ports, LEDs, and cables on the chassis; and details of temperature sensors. You can also view device authenticity, vulnerabilities, end of support information, and SIRT advisories for the device. In addition, you can view a graph of component-wise performance, threshold levels, events, and anomalies.

    • Interfaces: Paragon Automation executes tests to determine the state of the device interfaces. You can view the total number of pluggables in the device, port flapping issues, input traffic range, output traffic range, input errors, and output errors related to the interface. In addition, you can view performance, threshold levels, and events for all interfaces on a graph.

    • Software: Paragon Automation validates whether the version of the OS installed is genuine or not. You can view general information (software version, vendor, model of device on which the software is installed) and End-of-Life (EOL) date and number of Security Information Response Team (SIRT) advisories present for the device.

    • Configuration: Paragon Automation validates the compliance of the configuration committed on the device with Center for Internet Security (CIS) benchmark. You can view the compliance score, the configuration committed on the device, and the backup configurations.

    • Routing: Paragon Automation executes tests to determine that the states of all BGP, IGP, RSVP, LSP, and LDP neighbors are healthy. In addition, you can view information on number of routes in the routing information base (RIB) and forwarding information base (FIB) tables.

    • Connectivity: While onboarding a device, Paragon Automation uses test agents to automatically run tests, using synthetic traffic, to check device connectivity and cable issues. The device connectivity tests are run from the device being onboarded to neighboring devices, edge routers, Internet endpoints (such as DNS servers), and to hosts in Google (GCP), Microsoft (Azure), and Amazon (AWS) cloud. You can also re-run connectivity tests for one or more connections from the device. The data displayed includes:

      • The health of all connections from a device to edge devices, Internet endpoints, cloud providers, and neighboring devices.

      • Packet loss, response time, and error seconds as timeline graphs for ping, DNS, and HTTP tests.

      • Events and logs that display test result details.

      • Periodically refreshed connectivity data for all connections.

    [See View Results of Automated Device Tests.]

  • Troubleshoot and Manage Devices—You can troubleshoot and manage the devices in your network from the Observability > Health > Troubleshoot Devices page. On this page, you can view the:

    • Number of events for which urgent action is needed.

    • Number of events for which action is needed.

    • Number of connected devices.

    • Number of disconnected devices.

    You can perform additional tasks such as, view device details, reboot a device, back up configurations, upgrade a device, or assign a device to a site.

    In addition, you can troubleshoot the listed issues by clicking a hostname to navigate to the Observability > Health > Troubleshoot Devices > Device-Name page. Use the Overview tab to view the results of health checks that Paragon Automation performs on the network and the network devices. Use the Inventory tab to view details about the hardware components of the chassis and associated interfaces, information on licenses applied on the device, and features available on the licenses.

    [See About the Troubleshoot Devices Page.]

  • Manage configuration backups—You can view the list of all the configuration backups from the Configuration Backup page (Inventory > Devices > Configuration Backups). You can view the details of the backed-up configurations, preview, and restore backed-up configuration.

    [See About the Configuration Backups Page.]

  • Manage configuration templates— Configuration templates enable you to create customized configurations and deploy the configurations to one or more devices. You can view, add, edit, or delete configuration templates and preview the configuration template before deploying the configuration on a device, from the Configuration Templates page (Inventory > Devices > Configuration Templates).

    [See About the Configuration Templates Page.]

  • Manage software images—You can manage the device images from the Software Images page (Inventory > Devices > Software Images). You can view the details of the available device images, add images, and delete images.

    [See About the Software Images Page.]

Observability

Paragon Automation enables you to view your entire network topology, monitor network health, be notified of any anomalies in the network, and also get guidance on the remediation of these anomalies. With observability, Paragon Automation monitors and analyzes the network and its components by using key performance indicators (KPIs), device logs, and metrics, and notifies you about network issues through alerts and alarms. Additionally, Paragon Automation runs connectivity tests using synthetic traffic to identify connection issues between devices in your network.

The timely detection of anomalies enables you to take prompt action and minimize the impact of any issues that occur.

  • Device Events—Paragon Automation generates notifications based on the data collected from the devices in the network. These notifications highlight the issues that need attention and how they might affect the network. You can view and monitor device logs, alarms, and alerts from the Device Events (Observability > Health > Events) page. You can also configure e-mail notifications of device events.

    • Alerts—Paragon Automation generates various alerts to notify you about significant events within the network. You can acknowledge and filter alerts from the Alerts tab.

    • Alarms—You can use Paragon Automation to manage alarms that are generated by a device when an undesirable event that needs correction has occurred. You can acknowledge and filter alarms from the Alarms tab.

    • Device logs—Paragon Automation automatically collects device system logs (syslogs) from the network devices. System logs are collected every three minutes and stored securely. Device logs can be used to monitor the device health and status.

    [See About the Events Page.]

  • Event template configuration—Paragon Automation enables you to track the events generated (alerts or alarms) for an organization by using event templates. In the event template, you can specify the alerts or alarms (event types) that you want to monitor and specify e-mail recipients who will be notified when these events are detected in your network. If an event template is configured and applied to the organization, the generated alarm or alert list is filtered based on the events configured in the template. If no template is configured and applied to the organization, all the generated alerts or alarms are listed. You can also receive notifications on external applications such as slack by enabling webhooks.

    [See Manage Event Templates.]

  • Set device positions in the topology map by coordinates—In the Topology page (Observability > Network > Topology), you can reposition the devices on the map, that are not associated with a site, by setting their geographical coordinates (latitude and longitude). This feature is useful if you want to mimic your actual topology on the map. You can reposition devices by modifying coordinates in a CSV or GeoJSON file or by manually positioning the device on the map. To manually position devices, move the device to a point on the map and select Layout > Set Coordinates from Map in the right-click menu. After repositioning, you can also reset the coordinates to the default values by clicking Layout > Reset by Coordinates in the right-click menu.

    [See View Network Topology Details.]

  • Collapse devices and links into clusters and bundles, respectively—On the topology map, you can switch to the cluster view to collapse proximal devices into clusters and proximal links into bundles. You can perform this by clicking the cluster view icon on the topology menu bar in the Topology page. The cluster view reduces clutter in the topology map for large-scale networks.

    [See View Network Topology Details.]

  • Prioritize troubleshooting using alerts on the network topology map—Paragon Automation displays alerts for each host on your network on the Topology page (Observability > Network > Topology). If you hover over the icon displayed on a device, you can see the error count and the type of alerts such as Urgent Action Needed and Action Needed. This enables you to prioritize troubleshooting issues in the device based on the error count and the alert type.

    [See About the Device Tab.]

  • Automatically monitor device health KPIs and detect anomalies—During device onboarding and when a device is in operation, Paragon Automation monitors key performance indicators (KPIs) related to a device's health, and then automatically detects any anomalies that occur. You can monitor device health KPIs and view anomalies on the Hardware accordion of the Device-Name page (Observability > Health > Troubleshoot Devices > Device-Name).

    Paragon Automation monitors the following device health KPIs:

    • Temperature (Routing Engine and Routing Engine CPU)

    • CPU Utilization Percentage and CPU Load Average (Routing Engine, FPC)

    • Memory Utilization Percentage (Routing Engine, FPC)

    • Fan RPM and RPM Percentage

    [See Hardware Data and Test Results.]

Trust and Compliance

Paragon Automation periodically checks whether a target's configuration, integrity, and performance comply with predefined security benchmarks. The term target refers to devices and device components. The outcomes of these checks are distilled into a single trust score that tells you how trustworthy a device is.

Paragon Automation provides the following features to protect the network from threats and vulnerabilities and maintain trust in the network:

  • Automatically monitor the integrity of the hardware and software in the network—Paragon Automation automatically collects information about the targets on the network and the version of software running on them. It then compares the collected information against the information maintained in Paragon Automation database to ascertain whether the devices on the network and the software running on these devices are in line with the vendor's recommendations. In addition, Paragon Automation notifies you in advance when a device or the software running on the device nears its End of Life (EOL) date.

    [See Integrity of the Hardware and Software on the Network.]

  • Determine device trustworthiness using a generated trust score—Paragon Automation periodically generates a trust score for each network device and uses that score to determine the trustworthiness of each device. A device's trust score is computed based on the device's configuration, integrity of the device's hardware and software, and the Security Incident Response Team (SIRT) advisories that affect the device. Network administrators can use the trust score to assess the performance of targets over a period of time and perform corrective action to improve the trust score.

    [See Trust Score Overview.]

  • Generate trust score for targets based on a predefined trust score plan—Paragon Automation provides a trust score plan which defines the factors on which the trust score of a target should be based. The trust plan consists of prerequisite, variable, and reputational factors and the weighting assigned to each of these factors, which contribute to the trust score of a target.

    [See Trust Plans Overview.]

  • Generate periodic snapshots of targets—Paragon Automation generates periodic snapshots of targets in the network. Network administrators can use these snapshots to evaluate the performance of the targets over time. Snapshots provide information about trust score trends and help administrators take the required action when the trust score has a negative trend.

    [See About the Snapshots Page.]

  • Track SIRT advisories—Paragon Automation tracks the Juniper Networks Security Incident Response Team (SIRT) advisories that affect the devices in the network. These SIRT advisories provide information about the maintenance tasks that network administrators need to perform to resolve the vulnerability on time and maintain trust in the network.

    [See Vulnerabilities Overview.]

  • Ensure compliance with standard security benchmarks—Paragon Automation automatically performs scans to check whether the targets in the network comply with the security benchmark documents defined by the Center for Internet Security (CIS). Security benchmark documents contain predefined rules that targets in the network must comply with, so that the network is secure from threats.

    [See About the Compliance Benchmarks Page.]

  • Customize benchmarks document—You can use Paragon Automation to customize benchmarks document by creating tailorings documents. Tailorings documents contain the rules and parameters that the devices on the network should comply with. Based on individual network requirements, an administrator can modify the values defined in the tailoring document and apply it on the network.

    [See About the Compliance Tailorings Page.]

  • Create device-specific checklists—You can use Paragon Automation to create device specific checklists and use them in compliance scans. A checklist is based on a checklist template, which is based on a benchmarks document. You can update a checklist by importing previous scan reports and modifying the rules.

    [See About the Compliance Checklist Page.]

  • Automatically perform scans and generate reports—Paragon Automation runs periodic scans to ensure that the targets and the network are trustworthy. After every compliance scan, Paragon Automation generates a report. A network administrator can use these reports to analyze the trust score of the targets that were scanned, and obtain more information about trust score trends.

    [See Compliance Scans Overview.]

  • Notify about known problems in devices—Paragon Automation provides a list of known issues in the devices in your network on the PBNs page. The proactive bug notifications (PBN) feature in Paragon Automation helps you identify potential bugs in the devices so that you can plan software and hardware upgrades. Problems that affect the devices in the network are categorized according to their severity-level (Critical, Major, and Minor) and are displayed in the insights bar at the top of the page. This makes it easy to identify devices that need software upgrade.

    [See About the Proactive Bug Notifications Page.]

Administration

Paragon Automation provides the following administration features to manage users, sites, and organizations:

  • Multiple user authentication methods—You can log in to Paragon Automation using the following methods:

    • Using your Paragon Automation account

    • Single Sign-On (SSO) using identity providers—A superuser can configure third-party identity providers to authenticate users in Paragon Automation. Users can then sign in using their login credentials.

    [See Authentication Methods Overview.]

  • User accounts—Superusers create and manage all users in an organization. Based on your role, you can modify your personal account information and password. You can also enable or disable two-factor authentication or e-mail notifications, change roles, and so on.

    [See Manage Your Paragon Automation Account.]

  • Predefined User Roles—Paragon Automation provides four predefined roles to manage access privileges of users, based on the tasks that they need to perform.

    • Super User—Creates an organization, adds users, adds sites, adopts devices, and so on. This role maps to the system administrator persona.

    • Network Admin—Monitors, verifies, and troubleshoots an organization's network. This role maps to the network architect or a network planner persona.

    • Observer—Monitors events in the organization's network but cannot take corrective action. This role maps to the Network Operation Center (NOC) engineer persona.

    • Installer—Installs and onboards devices. This role maps to the field technician persona.

    [See Predefined User Roles Overview.]

  • Organization and Sites—In Paragon Automation, an organization is an entity that contains a group of sites, and devices are installed on sites. A superuser can create and manage sites and site groups in an organization. To apply device management functions, a device must be assigned to a site.

    [See Organization and Sites Overview.]

  • Generate API tokens to authenticate users—Paragon Automation uses API tokens to securely authenticate users who request access to resources through REST APIs and also the GUI.

    [See Manage API Tokens.]

  • Configure webhooks for receiving notifications—Paragon Automation allows a superuser to configure webhooks. Webhooks send notifications to third-party applications, such as Slack, when subscribed events, such as alerts, audit logs, device alarms, and change in device status, occur on the managed devices. Internet connectivity is required for Paragon Automation to connect to third-party applications, such as Slack.

    [See Configure Webhooks to Receive Event Notifications.]

  • View and export device inventory—You can perform the following tasks from the Inventory page (Inventory > Network Inventory):

    • Onboard (adopt) a device connected to your network.
    • Release an onboarded device.
    • View and export inventory information.
    • View and modify device operational status.
    • Assign a device to a site.

    [See About the Inventory Page.]

  • View Audit Logs—Paragon Automation records audit logs that are used for tracing user-initiated events and for maintaining a history of user's activities, such as accessing an organization or updating an event template. Audit log entries include details such as the name of the user who initiated the task, the source IP address, and date and time of task initiation. You can filter audit logs based on the user name, log message, site name, or the log time period.

    [See About the Audit Logs Page.]

Service Orchestration

Service orchestration is the process of designing, configuring, validating, deploying, and monitoring a network service. Paragon Automation automates the entire life cycle of a network service by providing workflows that execute the tasks to be completed to deliver a service. You can provision various network services by using predefined service designs written in YANG to provision services. The Service Catalog is an inventory of service designs, which are templates that provide guidelines and parameters for instantiating a service. A service instance defines the elements of a service. The instruction to create, modify, or delete a service instance is a service order. After you initiate a service order and publish it, Paragon Automation provisions the service in the network. After provisioning, Paragon Automation monitors the service by automatically setting up Juniper® Paragon Insights and Juniper® Paragon Active Assurance instances to monitor network health and measure service quality.

  • Automate service provisioning using service designs—A service design includes service models, rules for allocating resources, templates to transform service instances to configurations for deployment on devices, and integrations with Paragon Insights and Paragon Active Assurance for monitoring a service after provisioning. The Service Catalog is an inventory of service designs that Paragon Automation provides to provision a service in the network. The inventory of service designs includes:

    • Infrastructure service design to onboard and deploy devices to the network.

    • Routing and Layer 3 address service designs to configure network resource pools for the infrastructure service.

    • Topology and VPN service designs to configure network resource pools for the L3VPN service.

    • L3VPN service design to provision and monitor L3VPN services in the network.

    You can upload service designs using the service orchestration cMGD CLI only.

    [See Service Design Overview and About the Service Designs Page.]

  • Manage service instances—You can use Paragon Automation to create, modify, and delete or deprovision service instances based on predefined guidelines and parameters specified in service designs. A service instance contains a detailed description of a specific network service. When you submit an instance using the Publish button on the Service Instances page, Paragon Automation provisions the service in the network.

    [See About the Service Instances Page.]

  • Provision Layer 3 VPN service—Paragon Automation allows you to provision L3VPN service in the network. An L3VPN service instance includes general information such as customer name, VPN profiles and service details; and site-specific details such as site names, addresses, and site network access details. You can view a graphical representation of your service topology and a summary of the service instance. You can also export the service instance details in the JSON file format for editing or debugging.

    [See L3VPN Service Provisioning Workflow.]

  • Monitor service orders—When you create, modify, or delete a service instance, you initiate corresponding service orders for these operations. Each type of service order has a corresponding automated workflow to execute the order. Paragon Automation activates the workflow for a service order when you publish the service order. You can view the inventory of all service orders that you upload and publish on the Service Orders page. The Service Orders page displays the state of execution of service orders and the status of tasks executed to fulfill the service order.

    [See About the Service Orders Page.]

  • Monitor service provisioning workflows—Paragon Automation uses automated workflows or series of tasks to provision services in the network after you initiate a service order. A service order is an instruction to create, modify, or delete a service instance. You can monitor the workflow execution status of a service order from the Workflows page. If a workflow fails, you can access detailed logs to quickly troubleshoot and resolve issues.

    [See About the Workflows Page and View Workflow Run Details.]

  • Manage customer inventory—You can use Paragon Automation to create and manage an inventory of your customers. Customer refers to a user or an organization that utilizes a service from a service provider. You can create and manage your customer inventory by adding customers, editing or deleting customer details, and view services provisioned for customers from the Customer Inventory page.

    [See About the Customer Inventory Page.]

Active Assurance

Active Assurance is a programmable test and service assurance solution, which automates testing processes and gains continuous insights on network quality, availability, and performance. Active Assurance uses Test Agents, which are measurement points in your network. Test Agents generate, receive, and analyze network traffic and therefore enable you to continuously view and monitor both real-time and aggregated result metrics. You can deploy the Test Agents at strategic locations in your network and install them on Junos OS Evolved routers, x86 hardware, or on virtual machines. If you are using Juniper Networks® MX Series Universal Routers and Juniper Networks® PTX Series Routers, Paragon Automation uses real-time performance monitoring (RPM) for collecting the metric data.

Paragon Automation provides the following Active Assurance features:

  • View Test Agents in your network—Test Agents are measurement points that you can deploy at strategic locations in your network for continuous quality monitoring.

    Use the Paragon Automation GUI to view the list of all Test Agents that you installed in your network from the Test Agents (Inventory > Active Assurance > Test Agents) page. On this page, you can:

    • View the total number of Test Agents in your network.

    • View the number of Test Agents that are in use.

    • View the details of each Test Agent, such as, the location of the Test Agent, system information, interface, and so on.

    [See About the Test Agents Page.]

  • Use Tests and Monitors to measure metrics—Monitoring Key Performance Indicators (KPIs) such as the response time, congestion, and reachability is important to gauge the quality of your network. You can use Paragon Automation to create and run on-demand Tests and Monitors to monitor KPIs and to gain insights into your network's health, performance, and quality.

    You can create a Test if you want to measure metrics for a specified interval. You can create a Monitor if you want to measure metrics indefinitely. Use the Measurement Designer (Observability > Active Assurance > Measurement Designer) page to create and run Tests and Monitors.

    At the time of creating a Test or a Monitor, you configure the threshold values for various metrics. If there is a violation, then the Test fails or the Monitor generates an event.

    When you run a Test or a Monitor, Paragon Automation instructs the Test Agents to send or receive traffic using the selected protocols through measurements. Each measurement produces one or more streams of metrics. The Tests or Monitors evaluate these streams and the summary of the Test or Monitor results is displayed on the Test Details (Observability > Active Assurance > Tests > Test- Name) or Monitor Details (Observability > Active Assurance > Monitors > Monitor-Name) pages. You can look at the stream graphs to determine the cause for the violation.

    You can view the list of all Tests that you have created on the Tests page (Observability > Active Assurance > Tests). On this page, you can also perform additional tasks such as view details of each test, copy REST API request URL, download the test result as a JSON file to your local system, and so on.

    You can view the list of all Monitors that you have created and their details on the Monitors page (Observability > Active Assurance > Monitors).

    [See Tests and Monitors Overview.]