Go Agent v0.2.2
June 21, 2023
-
Change
Modified the agent configuration method.-
The whatap.conf files are now configured for each process.
-
The whatap.conf file must have been created before running the process.
-
The previous /usr/whatap/agent/whatap.conf file uses only the whatap-agent service.
Note-
It is recognized as an agent for each process for data separation.
-
In the past, multiple processes were all recognized as an agent, and their data was integrated.
TipFor more information about agent configuration, see the following.
-
-
Change
For agent IPC communication, UDP has been changed to TCP.-
The
net_udp_host
andnet_udp_port
options remained without change. -
The added
net_ipc_host
andnet_ipc_port
options are available.
By default, the IP of 127.0.0.1 and the port number of 6600 are used. For update, change the user application and the whatap-agent service configuration file. The changes are applied after restarting.
- The whatap.conf file of the user application has been changed.
whatap.conf# Change the host.
net_ipc_host=127.0.0.1
# Change the port.
net_ipc_port=6601- The whatap.conf file of the whatap-agent service has been changed.
vi /usr/whatap/agent/whatap.conf
# Change the port.
net_ipc_port=6601- Restart
service whatap-agent restart
-
-
Change
The agent naming convention has been changed.-
Previous:
{type}
-{ip2}
-{ip3}
-{process}
-
Now:
{type}
-{ip2}
-{ip3}
-{cmd}
-{cmd_full}
Note-
{cmd}
: Process name. The value of the executable args[0]. -
{cmd_full}
: All the lines of the commands are hashed. All of the executable args. -
When using the same process and arguments, the agent name can be duplicated. The
app_name
option can be arbitrarily set in whatap.conf. For more information, see the following. After configuration, be sure to restart the application.
-
-
Change
Modified the memory usage.The memory usage appears with the sum of
HeapInUse
andStackInUse
inruntime.MemStats
.