Skip to main content

Kubernetes Agent v1.5.7

March 7, 2024

  • Feature The whatap-node-helper collects images and performance data from node disks and containers. After adding the logging and configuration functions for the container, you can handle the options of the corresponding function.

    • collect_volume_detail_enabled Boolean

      Default true

      In the node agent, use the exec df command for all containers to enable searching the container volume information. You can enable the function to collect storage usage and volume data for all containers running on the node.

    • inject_container_id_to_apm_agent_enabled Boolean

      Default true

      It enables container ID injection using exec in the WhaTap APM container. The ID of a container identified by WhaTap APM can be automatically extracted and injected into the APM tool, which can be used to associate the performance monitoring data with the container.

      Note

      This option is available starting with Java agent 2.2.33 or later.

  • Changed When collecting Kubernetes events from the master agent, the logic that stops collecting duplicate events when the agent is restarted has been deleted. It modified to perform the duplicate event drop logic on the server side.

    Note

    Cause of duplicate collection: When the master agent is restarted and the event is still stored in the Kubernetes cluster, the event is to be read again even if it has already been collected, because the agent does not detect it.

  • Fixed Through the watchLog feature, you can monitor a specific log file (e.g. /var/log/message) on the node system from the WhaTap dashboard. We fixed the bug where additional log collection fails if the file was changed by the system's log rotation logic.

Info

Agent download: kube_mon_1.5.7.tar