> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/solution-guides/best-practices/cdev_test_settings_alerts.md).

# Self-Serve Test Settings and Alerts for Connected Devices

## Product Update Notice

As ThousandEyes continues to evolve, navigation and terminology may differ from earlier guides or screenshots. This document reflects the current General Availability (GA) experience for Connected Devices.

## Prerequisites

This guide is intended for ISP network operations and product teams familiar with ThousandEyes. To optimize monitoring and alerting for Connected Devices, ensure you:

* Know how to deploy and manage Connected Devices Agents.
* Understand how to create and manage network performance tests and custom alerts.
* Are aware of your current agent deployment and versioning. All agents must be running version 8.
* Have knowledge of your network's structure and relevant use cases, such as regulatory, pre-deployment, lab, or targeted device monitoring.

## Introduction

This guide outlines best practices for using Self-Serve Test Settings and Alerts with Connected Devices. These features enable you to manage test creation, agent assignment, alerting, and remote upgrades, allowing for faster, more flexible, and scalable monitoring.

### Target Audience and Use Cases

These features are designed for:

* **Universal Test Deployments**: Assign tests or alerts across your agent fleet when a uniform configuration is needed.
* **Targeted Testing**: Assign up to 500 agent IDs for specialized monitoring, ideal for smaller deployments or precise targeting.
* **Lab and Pre-Deployment Environments**: Experiment with test configurations or conduct pre-deployment device testing with a limited number of devices.
* **Regulatory and Compliance Testing**: Document and manage tests for compliance or funding requirements across devices.

### Best Practices for Test Settings

#### 1. Agent Versioning

**Ensure all agents are running version 8** to access these features. Plan and complete upgrades for compatibility.

#### 2. Test Assignment Strategies

* **Assign to All Agents**: Use for scenarios requiring universal coverage. Offers scalability and low maintenance.
* **Assign to Specific Agent IDs**: Enter up to 500 agent IDs per test for precise targeting. Ideal for labs, pilots, or small device groups. Tip: Maintain a reference list or spreadsheet of agent IDs for easier configuration.
* **Organize with Tags and Groups**: Use descriptive group names and tags to efficiently filter, manage, and report on test suites.

#### 3. Test Configuration

* **Templates**: Start with recommended templates, such as Network Tests, and customize as needed.
* **Advanced Settings**: Adjust test duration, packet frequency, and protocols to meet monitoring goals.
* **Scheduling**: Set intervals to balance data granularity with network and agent load (e.g., 15 minutes for frequent insights).
* **On-Demand Testing**: Enable trigger tests for immediate troubleshooting via UI or API.

#### 4. Bandwidth Awareness

Review estimated network load before deploying high-frequency or bandwidth-intensive tests to avoid impact.

### Best Practices for Alerts

#### 1. Alert Rule Creation

* **Granularity**: Create separate alert rules for key metrics (latency, loss, jitter) as required.
* **Scope**: Apply alert rules to all agents for broad coverage or up to 500 agent IDs for targeted monitoring.
* **Severity and Thresholds**: Define severity levels (info, minor, major, critical) and set thresholds to prioritize and filter alerts.

#### 2. Notification and Integration

* **Channels**: Enable real-time notifications via webhooks, email, or supported integrations (PagerDuty and ServiceNow integration coming soon).
* **Alert Management**: Regularly review, snooze, and refine alert rules to reduce noise and enhance response.

### Monitoring and Data Analysis

* **Single-Agent View**: Use the Constant Care view to assess individual agent performance and troubleshoot device-specific issues.
* **Aggregate Analytics**: Access the Analytics module for fleet-wide trends, comparisons, and historical data reviews.

### Summary and Recommendations

* Upgrade all Connected Devices agents to version 8.
* Use "assign all agents" for broad coverage, or up to 500 agent IDs for targeted monitoring.
* Organize tests and alerts with clear names, tags, and groups.
* Continuously monitor agent and network performance, and refine alerting to minimize false positives.

For additional support, consult the Connected Devices documentation or contact your ThousandEyes representative.