AI for Network Leaders — Powered by Selector

Join us in NYC on March 25th

AI for Network Leaders — Powered by Selector

Join us in NYC on March 25th

On this page

The Brain Behind the Pings: Understanding the Synthetics Control Plane

In today’s interconnected world, a fundamental question plagues every network administrator and SRE: “Is my network running well?” The answer, often elusive, is precisely what synthetics aims to provide. By deploying a vast fleet of specialized probe agents, synthetics continuously monitors critical network health metrics, including latency, packet loss, jitter, and custom reachability checks, providing an unparalleled view into your network’s performance.

While the core concept of sending pings might seem simple, the magic and the complexity lie within the control plane of a robust and scalable synthetics system. This isn’t just about sending ICMP packets; it’s about orchestrating a distributed system of thousands of probes to deliver accurate, real-time insights across a large-scale network.

Designing the Control Plane: The Core Pillars

A well-designed synthetics control plane is the backbone of its effectiveness. It’s what transforms raw ping data into actionable intelligence. Let’s explore the key mechanisms that enable this sophisticated orchestration.

This section explores the control plane mechanisms necessary for managing a network of synthetics monitoring probes. Understanding these mechanisms offers valuable perspectives on how synthetics effectively handles distributed network monitoring:

Managing Large-Scale Agent Deployments:

Imagine deploying thousands of synthetics probes across various data centers, cloud regions, and remote offices. The control plane is your central hub for this monumental task. It facilitates automated deployment, upgrades, and health monitoring of these numerous probes, ensuring they are always running and reporting as expected. This involves sophisticated deployment strategies, version control, and continuous health checks to identify and address any agent-related issues proactively.

  1. Synthetics probe installation

To start with, the customers install a fleet of synthetics probes in their environment. Selector symthetics probes can be installed as Linux Debian/RPM packages or as Docker containers. The probes can be installed on Linux or Windows hosts, networking switches, and routers. 

Customers often use Ansible or other fleet management tools to do the install. The artifacts to install are fetched from the Selector SaaS platform. All the agents auto-connect to the SaaS instance on startup to register. Connected probes are marked as registered but do not participate in synthetics yet until further action is taken.   

  1. Synthetics inventory management

Synthetics is driven by inventory configuration on the Selector SaaS platform. All probes that register with the SaaS platform should be added to the synthetics inventory. Inventory for probes can be added even before the probes are installed.

  1. Health check, performance metrics, and logs from probes

Synthetics probes maintain a constant connection to the Selector SaaS platform, transmitting continuous health data to confirm their operational status. To minimize host system resource consumption, probes are designed to be lightweight. Additionally, they provide performance metrics for monitoring resource usage.

Given their deployment within customer environments, probes proactively send critical logs to the SaaS platform. This ensures the availability of necessary data for debugging and enhanced visibility during triage. 

Example of issues that can be alerted on based on the metrics:

  • The host system has a clock skew and is out of sync with NTP servers
  • Ping iterations match the configured values
  • State of agents registered but not operational

Implementing Pivot-Based Probes Grouping:

Raw data is only as good as its organization. The concept of pivot-based grouping is a powerful mechanism within the control plane that enables efficient organization and analysis of network monitoring data. Instead of just a flat list of probes, the control plane allows for the dynamic grouping of probes based on various “pivots”- geographical location, network segment, application served, or even custom tags. This will enable you to slice and dice your monitoring data to gain insights specific to certain parts of your infrastructure, enabling targeted troubleshooting and performance analysis. For example, you could quickly view all probes monitoring your e-commerce platform or all probes within a specific metropolitan area. 

Pivots are configured based on the inventory columns. Customers can select one or more specific columns to define as the pivot. This creates mesh instances of probes participating in synthetics within their instance. A probes can participate in multiple mesh instances.

In the example below, 12 probes participate in multiple meshes based on pivot tags Tag1 and Tag2. The four meshes are:

  1. DC1 Mesh with four probes
  2. DC2 Mesh with four probes
  3. Cloud Mesh with four probes
  4. Overlay Mesh with three probes
visualization of pivot based agent grouping, showing DC1 Mesh, DC2 Mesh, and Cloud Mesh connected bia Overlay mesh

Handling Configuration Management for Probes:

Consistency is key in a distributed system. The control plane plays a vital role in ensuring consistent and up-to-date configurations are applied to all monitoring probes. This includes managing which metrics to collect, the frequency of pings, target endpoints, and other related details. 

Some of the example configurations that are supported and can be configured from Selector SaaS

  • Ping frequency
  • Packets per iteration
  • Update source port and TOS values for ping packets
  • Traceroute configuration such as max hop, first packet TTL, packet size and more

The configuration is synced from Selector SaaS to all the probes.

Summary

Fundamentally, the synthetics control plane serves as the essential operational mechanism, the sophisticated manager directing a complex system of network probes. It is the component that translates a basic concept into a robust, adaptable infrastructure for addressing the critical query: “Is network performance satisfactory?” By understanding these fundamental functionalities, one develops a more comprehensive understanding of the complex technical design that underpins efficient and thorough network observation.

To stay up-to-date with the latest news and blog posts from Selector, follow us on LinkedIn or X and subscribe to our YouTube channel.

More on our blog

Beyond the Dashboard: Selector’s Patented Approach to Conversational Observability

For years, IT operations teams have been trapped in a frustrating paradox: the data they need to solve critical issues is right at their fingertips, yet entirely out of reach. Accessing it requires engineers to master complex, platform-specific query languages, dig through endless layers of dashboards, and hunt for the exact visualization that holds the answer. Under the intense pressures of modern speed, scale, and complexity, this rigid model is breaking down. At Selector, we recognized a fundamental opportunity to change how teams interact with their data. Our recently published U.S. patent application (US20250278401A1, filed March 2, 2024, and published September 4, 2025), titled “Dashboard metadata as training data for natural language querying,” outlines a transformative solution. By utilizing dashboard metadata, aliases, and user interaction data as training material, we empower operators to bypass structured queries entirely and obtain infrastructure insights using plain, natu

The Business Case for AI-Driven Observability in Network Operations

Modern network operations generate an extraordinary amount of telemetry. Metrics, logs, events, topology data, cloud signals, and service context all contribute to a richer picture of system behavior. As environments expand across cloud, data center, edge, and SaaS, the opportunity for operations teams is clear: when that telemetry is unified and understood in context, it becomes a powerful source of resilience, efficiency, and business insight. That is why AI-driven observability has become such an important priority for IT and operations leaders. Its value comes from helping teams move through complex environments with greater clarity. Correlated signals, contextual awareness, and shared operational understanding help teams identify issues faster, coordinate more effectively, and resolve incidents with greater confidence. For business leaders, the conversation is increasingly practical. They want to understand how observability investments contribute to uptime, team productivity, op

Solving the Ticket Noise Problem: What We Learned from Our ServiceNow Webinar

On March 18th, we hosted a session focused on a challenge that continues to undermine even the most mature IT operations teams: ticket noise.  It’s easy to dismiss noise as just “too many alerts”. But as we explored in the webinar, the real issue runs deeper. Ticket noise is a symptom of something more fundamental — a lack of correlation, context, and shared visibility across the stack.  If you weren’t able to attend, this blog walks through the key ideas, examples, and takeaways. And if any of this feels familiar, it’s worth watching the full session.  View “Solving the Ticket Noise Problem: Bringing Intelligence to ServiceNow”.  The Hidden Cost of Tickets Most organizations don’t struggle because they lack monitoring. In fact, the opposite is true — they have too much of it. Over time, teams adopt specialized tools for every layer of the environment: Each tool does its job well within its domain, but incidents don’t respect those boundaries. As discusse

このサイトは開発サイトとして wpml.org に登録されています。remove this banner のキーを使用して本番サイトへ切り替えてください。