Geneos ["Geneos"]
["Geneos > Netprobe"]["User Guide"]


System requirements

The following requirements must be met on the node machine where the Netprobe and Collection Agent are installed:

  • Bare metal:
    • Linux operating system (CentOS, RHEL or SUSE), or
    • Windows operating system
  • Kubernetes or OpenShift:
    • Linux operating system (CentOS, RHEL or SUSE)
  • Java 1.8 or higher.
  • A minimum Java heap size of 512MB is recommended for Collection Agent.
    If the agent is performing garbage collection too frequently as the volume increases, a larger heap size should be allocated.

Geneos requirements

  • Geneos Netprobe version 5.1.0 or higher.

Orchestrated environment requirements

The Netprobe for Orchestrated Environments requires either of the following:

  • OpenShift version 3.11 or higher.
  • Kubernetes version 1.15 or higher.

Network requirements

Specific inbound and outbound network ports must be accessible depending on which plug-ins and reporters are configured.

Collection Agent Plug-ins

  • StatsD plug-in — inbound UDP or TCP from all StatsD clients, 8125 by default.
  • Kubernetes plug-in — outbound TCP to Kubernetes API, 443 by default.


  • Kafka — outbound TCP to Kafka brokers, 9092 by default.
  • TcpReporter and TcpReceiver — communication between the Collection Agentand Netprobe, operates on port 7137 by default.


The Kubernetes plug-in requires the following permissions:

  • Access to the Kubernetes API with permission to read pods and watch events in specific or all namespaces.
  • Read-only volume mounts for the following host directories:
    • /var/log/containers
    • /var/log/pods
    • /var/lib/docker/containers
  • If disk persistence is enabled, a read and write persistent volume is required. You can configure the required size for this volume.
  • In OpenShift, the Collection Agent container must run in privileged mode in order to use HostPorts and to access the host volume mounts.

Kubernetes log rotation

The table lists the supported options of the log rotation schemes of the log collector in the Kubernetes plug-in:

Log rotation scheme Description
Docker JSON driver


  • For OpenShift, see the official documentation to find out how to configure logs.
  • For Kubernetes, configure log rotation in /etc/docker/daemon.json:
      "log-driver": "json-file",
      "log-opts": {
        "max-size": "100m",
        "max-file": "10"
Logrotate create mode Supported
Logrotate copy mode Not supported
Logrotate copytruncate mode Not supported
Collecting from compressed log files Not supported