Skip to main content

Troubleshooting

Check for possible problems upon database agent installation.

Firewall configuration checking​

Unblock your firewall. Monitoring data cannot be sent to the server if the TCP outbound firewall is set for the WhaTap server.

How to check the firewall​

It is normal only when the following connection-related information appears after executing the telnet command. (telnet [Server IP] [Server Port])

Example
$ telnet 52.193.60.176 6600
Trying 52.193.60.176...
Connected to 52.193.60.176.
Escape character is '^]'.
Note

The WhaTap collection server data can be found in Project Menu > Management > Agent Installation.

Constraints​

Multiple regions impossible to be selected as a single project​

  • In the WhaTap monitoring service website, when creating a project, you cannot select multiple regions. When using multiple regions, create separate projects.

  • If servers exist in multiple regions as in the cloud environment, the collection servers must be located in each region to avoid constraints on the performance data collection such as network latency.

  • WhaTap builds collection servers for each region to meet customer requirements.

Duplicate agent names (ONAME) impossible to be used​

WhaTap DBX monitoring uses the agent's IP address and port to identify the agent. If the database server to be monitored in the user environment uses the same IP and port, the WhaTap server cannot identify the server instance.

  • If the server instance is not dynamically expanded, you can bypass it by manually setting a name for database identification by seeing the following.

  • If the databases to be monitored use internal addresses or duplicate IPs due to network virtualization, use separate database naming patterns by seeing the following.

DB roles and agent configuration​

There are menus where data is not viewed depending on the DB roles and agent configuration. See the following to assign the required roles and set the agent options.

Note

Example shows a monitoring account creation as whatap: create user whatap with password ‘DBPassword’;

MenuDB options and rolesAgent CONFIG.Remarks
Basic menugrant PG_READ_ALL_STATS to whatap;-PostgreSQL V2, DBX agent v1.6.15 or later
Dashboard > Slow queryDB parameter:
log_min_duration_statement=500
(e.g. SQL records taking 500 ms or more)

DB role
grant PG_READ_ALL_SETTINGS to whatap;		xos.conf
slow_query_interval=30 (Default 30 seconds)

whatap.conf
slow_query_log=ON		-
Instance monitoring > Session killalter user whatap with SUPERUSER;

In case of using AWS RDS:
grant RDS_SUPERUSER to whatap;		--
Analysis > Top objectgrant select on all tables in schema {schema_name} to whatap;whatap.conf
pg_object=true		DBX agent v1.6.15 or later
The lists in the Bloating and Age tabs may not be viewed when the thresholds (size, ratio) are not exceeded even if the roles and agent options have been configured.
Stat/Report > Database sizegrant usage on schema {schema_name} to whatap;whatap.conf
tables=true		It is the role required to view the table size under the Database size menu.
Object information (Object detail) modal windowgrant select on all tables in schema {schema_name} to whatap;-Pop-up window that appears when the table is clicked in Top object, Database size, and SQL details (Plan). With no role, the column list does not appear.