Kentik Synthetics Agents

The following topics provide a high-level overview of Kentik's ksynth family of synthetics agents:

Notes:
- For a general explanation of Synthetic Monitoring in Kentik, see Synthetics Overview.
- For information on specific modules within the Synthetics section of the Kentik portal, refer to the articles listed under Synthetics in the Contents tab of the KB.
- For assistance with any aspect of the agent setup process, please contact Customer Support.

 

About Synthetics Agents

Kentik is able to perform continuous synthetic performance testing from and to network locations both within your infrastructure and elsewhere around the Internet. These tests are enabled by Kentik’s ksynth family of software agents for synthetic monitoring. Kentik offers two distinct types of ksynth agents (see Synthetic Agent Types), each of which may be used in either global or private deployments (see Synthetic Agent Deployments).

 

Synthetic Agent Types

The ksynth family of software agents for synthetic testing includes the following agent types:

  • Network Agent: Available since 2020, our stable and well-tested “classic” synthetic agent is optimized for all network layer synthetic test types as well as the HTTP web test (see Synthetic Test Types).
    Note: This agent can't be used for Page Load tests.
  • App Agent: Currently in Beta, the app agent runs all of the tests supported by the network agent but can also run an instance of Headless Chromium (Google Chromium running in a headless/server environment), which enables Page Load tests.
 

Synthetic Agent Deployments

Kentik's synthetic testing agents are used in the following types of deployments:

  • Global Agents: Available to every customer that has activated our synthetic monitoring services, "global agents" are the agents in the Kentik Global Agent Network, a worldwide network of Kentik-maintained ksynth agents. Hosted in data centers and public clouds, these agents enable performance testing to and from key Internet hubs worldwide. Global agents include both network agents and app agents (see Synthetic Agent Types).
    Note: In some portal contexts, the subset of global agents that is deployed in the infrastructure of key cloud service providers (AWS, GCP, Azure, IBM, etc.) is referred to separately as "Public Cloud" agents.
  • Private Agents: Every Kentik customer can deploy as many ksynth agent instances as they care to in their own on-prem and/or cloud infrastructure (no additional license required). These private agents are for the exclusive use of the customer who deploys them (not available to other Kentik customers). Private agents may be either network agents or app agents.
 

ksynth Deployment Considerations

The following considerations apply when deploying either the network agent or the app agent version of ksynth:

Note: For additional deployment considerations that are specific to the network agent, see Network Agent Deployment.

 
top  |  section

ksynth Protocols

ksynth agents use the following protocols:

  • For communication between ksynth and Kentik's SaaS platform (US or EU): TCP 443 (HTTPS).
  • For network tests (IPv4 and/or IPv6):
    - Ping: ICMP or TCP (with option to specify target port)
    - Traceroute: UDP or TCP (with option to specific target port)
    - ICMP Echo ping.
  • For HTTP(s) or API Tests:
    - HTTP GET/ POST/ PUT/ PATCH sent to TCP port 80/443

Note: Future support is planned for UDP in ping and ICMP in traceroute.

 
top  |  section

Whitelisting ksynth

When running one or more ksynth instances on your network, the following IP address ranges should be whitelisted in your firewall rules to ensure that the agents can communicate with Kentik:

  • 208.76.14.0/24
  • 2620:129::/44
 
top  |  section

NTP Configuration

The server on which ksynth is installed must be configured as an NTP client to avoid known issues related to clock skew. If the NTP service is correctly configured, the following command should return successfully:

sudo ntpq -p


 
top  |  section

ksynth Security

The ksynth agent generates a unique identity and uses this to authenticate with the Kentik platform. The identity is stored in a local file to be used across restarts and upgrades.

© 2014- Kentik
In this article:
×