Cato Networks

Plugin: go.d.plugin Module: cato_networks

Overview

This collector monitors Cato Networks accounts through the Cato GraphQL API.

It discovers sites, collects site, device, and interface status, traffic and quality metrics, collects BGP peer status, and exposes Cato site/device/PoP/BGP topology data. Metrics for each selected site are emitted under a generated virtual node named after the Cato site and keyed by the Cato account ID and site ID. Site labels are still attached to metric series for grouping and aggregation.

The collector uses the Cato GraphQL API endpoint with an account ID and API key.

This collector is supported on all platforms.

This collector supports collecting metrics from multiple instances of this integration, including remote instances.

A Cato API key with permission to read account snapshot, account metrics, entity lookup, and site BGP status data is required.

Default Behavior

Auto-Detection

This collector does not auto-detect Cato accounts. Configure at least one job with account_id and api_key.

Limits

Site discovery is paginated and refreshed hourly. The optional site_selector filters sites before snapshot, metrics, BGP, topology, and generated site virtual-node creation. Account metrics use bounded concurrent one-site API requests to preserve per-Socket device and interface attribution. BGP status uses one per-site API request for each selected site that is not currently cached as having no BGP peers.

Performance Impact

The default interval is 60 seconds. Sites that return a successful BGP response with no peers are cached as non-BGP sites for about one hour, with deterministic per-site jitter across multiple collection cycles to avoid synchronized refresh bursts. If BGP is enabled on such a site, BGP metrics can appear after that cache expires.

Setup

You can configure the cato_networks collector in two ways:

Important

UI configuration requires paid Netdata Cloud plan.

Prerequisites

Cato API credentials

Create or obtain a Cato API key and account ID with read access to the required GraphQL API surfaces.

Configuration

Options

The following options can be defined globally: update_every, autodetection_retry.

via UI

Configure the cato_networks collector from the Netdata web interface:

1. Go to Nodes.
2. Select the node where you want the cato_networks data-collection job to run and click the :gear: (Configure this node). That node will run the data collection.
3. The Collectors → Jobs view opens by default.
4. In the Search box, type cato_networks (or scroll the list) to locate the cato_networks collector.
5. Click the + next to the cato_networks collector to add a new job.
6. Fill in the job fields, then click Test to verify the configuration and Submit to save.
   • Test runs the job with the provided settings and shows whether data can be collected.
   • If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.

via File

The configuration file name for this integration is go.d/cato_networks.conf.

The file format is YAML. Generally, the structure is:

update_every: 1
autodetection_retry: 0
jobs:
  - name: some_name1
  - name: some_name2

You can edit the configuration file using the edit-config script from the Netdata config directory.

cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
sudo ./edit-config go.d/cato_networks.conf

Examples

Basic

Collect Cato Networks account metrics and topology.

jobs:
  - name: account
    account_id: "12345"
    api_key: "replace-with-cato-api-key"

Metrics

Metrics grouped by scope.

The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.

Per site

These metrics refer to a Cato site.

Labels:

Metrics:

Per device

These metrics refer to a Cato Socket or vSocket attached to a site.

Labels:

Metrics:

Per interface

These metrics refer to a Cato site interface.

Labels:

Metrics:

Per bgp peer

These metrics refer to a Cato site BGP peer.

Labels:

Metrics:

Alerts

The following alerts are available:

Troubleshooting

Debug Mode

Important: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature.

To troubleshoot issues with the cato_networks collector, run the go.d.plugin with the debug option enabled. The output should give you clues as to why the collector isn’t working.

• Navigate to the plugins.d directory, usually at /usr/libexec/netdata/plugins.d/. If that’s not the case on your system, open netdata.conf and look for the plugins setting under [directories].

  cd /usr/libexec/netdata/plugins.d/
  

• Switch to the netdata user.

  sudo -u netdata -s
  

• Run the go.d.plugin to debug the collector:

  ./go.d.plugin -d -m cato_networks
  

  To debug a specific job:

  ./go.d.plugin -d -m cato_networks -j jobName
  

Getting Logs

If you’re encountering problems with the cato_networks collector, follow these steps to retrieve logs and identify potential issues:

• Run the command specific to your system (systemd, non-systemd, or Docker container).
• Examine the output for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem.

System with systemd

Use the following command to view logs generated since the last Netdata service restart:

journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep cato_networks

System without systemd

Locate the collector log file, typically at /var/log/netdata/collector.log, and use grep to filter for collector’s name:

grep cato_networks /var/log/netdata/collector.log

Note: This method shows logs from all restarts. Focus on the latest entries for troubleshooting current issues.

Docker Container

If your Netdata runs in a Docker container named “netdata” (replace if different), use this command:

docker logs netdata 2>&1 | grep cato_networks

API rate limits

Increase update_every or narrow site_selector if the Cato API reports rate limiting.

Connection, TLS, or proxy failures

Check DNS, firewall egress, TLS inspection, proxy settings, endpoint region, and the collector logs.