Skip to main content

Installation checking items

The database monitoring has been installed completely. After installation, check if the installation was successful by doing the following:

Checking the agent installation

Run the start.sh shell script file or the start.bat batch file from the installation path of the database agent. When you run the agent, it starts collecting monitoring data from the database. If the WhaTap logo is displayed in the terminal after executing the shell script, it is normally executed.

start.sh
$ ./start.sh

_ ____ ______
| | /| / / / ___ /_ __/__ ____
| |/ |/ / _ \/ _ `// / / _ `/ _ \
|__/|__/_//_/\_,_//_/ \_,_/ .__/
/_/
Just Tap, Always Monitoring
WhaTap DBX version X.Y.Z YYYYMMDD
Note

To use it like a daemon, execute the startd.sh command. However, it works only in the environment where nohup has been installed.

Info

When the DMX agent is run, the dmx and prx processes are executed.

Checking the logs

  • whatap.log

    All logs related to the agent startup and collection can be found in $WHATAP_HOME/logs/whatap.log path. If the size of the whatap.log file exceeds 25 MB, it is backed up with the file name of whatap.log.[n]. To clean up files, delete the files starting from the greatest (old) number.

  • prx.log

    This log file records major activities and events that occur during DMA (Direct Memory Access)-based data collection. Logs are recorded when the DMX agent is restarted. You only need to run the start.sh or startd.sh (execution of daemon) file once in the agent installation path.

Checking the agent processes

You can see active WhaTap DMX agent and prx processes with the following commands.

$ ps -ef|grep dmx

$ ps -ef|grep prx

Checking the monitoring

To check that the log has been normally uploaded from the server and the console has been registered normally, go to the initial screen of Whatap Monitoring Service. Select the project to check and then select Management > Agent List on the left. From Agent List, you can check the name of the database server. To set the names of database servers separately, see the following.