Kubernetes Agent v1.9.32

Includes Java Agent v2.2.68

October 26, 2026

Caution

Update the node agent and master agent images, including node helper, to public.ecr.aws/whatap/kube_mon:1.9.32 together. Don't update only the node agent and leave node helper on an older version. No separate operator upgrade or RBAC change is required.

• Feature Added collection of target process counts per node

  • Collects the number of target processes per node in the count field of kube_process_count.
  • Keeps sending count=0 after a target process exits, so you can detect a stopped process with a metrics event.
  • Specify the targets with collect_kube_node_process_metric_target_list in node helper. Each target must exactly match Name in /proc/PID/status, which Linux limits to 15 bytes (for example, kube-controller).
  • Follows collect_kube_node_process_metric_enabled and the existing collection and transmission interval settings. The default interval is 5 seconds.
  • Collection failures and stale data aren't sent as 0.
  • The existing kube_process data format is unchanged.
  Note

  If you use a 1.9.32 node agent with an older node helper, process count metrics aren't collected.

• Changed node helper retries when it fails to write the container ID to an APM container

  • Previously, node helper wrote the container ID (container.conf) only once, right after the container entered the Running state.
  • Fixed an issue where only some pods in the same Deployment lost their container link when the application started slowly and the agent file (for example, /whatap-agent/whatap_python for Python) didn't exist yet, or a transient execution error occurred.
  • On failure, retries up to 6 times, starting at 10 seconds and doubling the interval each time (up to 5 minutes).
  • Stops each execution that doesn't finish within 30 seconds.

Update notes

• When the update restarts the node agent pods, node helper reprocesses the running APM pods, so container.conf is also created for pods that lost their link in earlier versions. If the link still doesn't appear, restart the application pod.
• Containers that keep failing are retried up to 6 times, so the Failed to execute Whatap agent command lines in the node helper log may increase. Check the retry status with (attempt n/6, retry in …) or (attempt 6/6, giving up) at the end of each line.

Setting up process stop alerts

In a metrics event, specify kube_process_count, cmd1, and a filter for the nodes to monitor, then set count < 1 as the critical condition.

• Tags: onode, onodeName, cmd1, agentPcode, agentOid
• Field: count

Caution

Targets that never run on a node are also collected as 0. For example, don't apply a dockerd alert to containerd nodes in bulk.

Verify the values received by your project and how alerts are raised and resolved in your environment.

Info

Agent download: kube_mon_1.9.32.tar