Agent name identification

WhaTap basically uses the data collected from application servers to identify each server while collecting monitoring data. Basic information uses the application server as a unique identifier by a combination of application server's type, IP address, and such. If necessary, use the name set by the user or change the pattern to a unique value. The agent name must be unique.

The reason why the data extracted from the application server is used, is like the following. When a communication loss caused by the stop of the application server, network disconnection, or agent problem between the collection server and the agent, is restored, the continuity of the data from the reconnected agent is maintained.

Caution

• The agent names must be unique on a project basis.
• If the agent ID and name have been changed, previous data is not connected.

Note

• In WhaTap Monitoring, the object and agent can be used interchangeably as the monitoring target.

The default patterns used to identify the application server are as follows:

object_name - default pattern

{type}-{ip2}-{ip3}-{process}-{dockerid}-{ips}

The default pattern can be modified in whatap.ini.

Configuration	Description
type	Use the value set in whatap.app_name.
Ip#	When IPs are divided by period (.), the #th digit (from 0) is used.
process	Use the value set in whatap.app_name.
hostname	The server host name is used.
dockerid	Docker container ID
ips	Full IP (IPv4, IPv6)

• whatap.object_name String

  Default {type}-{ip2}-{ip3}-{process}

  It is an agent naming (ONAME) scheme to identify applications. An OID is created based on the ONAME.

  Note

  The setting is applied after restarting the whatap service. service whatap-php restart

• whatap.app_name String

  It is a component of the agent name (ONAME) to identify applications. The value corresponds to {type} of object_name.

  Note

  The setting is applied after restarting the whatap service. service whatap-php restart

• whatap.app_process_name String

  It is a component used in the agent naming (ONAME) scheme to identify applications. It sets the target process to collect data of the application server such as CPU and heap memory by using application process names. The value corresponds to the {process} of the object_name.

  Note

  The setting is applied after restarting the whatap service. service whatap-php restart

• whatap.okind String

  You can configure monitoring units by grouping multiple agents into "type-based" groups. This option allows you to monitor and manage multiple agents in groups, analyze performance metrics, and set the alerts.

  Note

  You can check it as a group option classified as By kind in the Dashboard and Analysis, Statistics menus.

• whatap.onode String

  You can configure monitoring units by grouping multiple agents into "node-based" groups. This option allows you to monitor and manage multiple agents in groups, analyze performance metrics, and set the alerts.

  Note

  You can check it as a group option classified for nodes in the Dashboard and Analysis, Statistics menus.