Creating Diagnostics¶

To diagnose what happened in the past in a Denodo server, follow these steps:

Gather the following files from the host where the Denodo server that you want to diagnose is running:
- From the directory <DENODO_HOME>/logs/vdp/, get vdp.log and its backup files if they exist (vdp.log.1, vdp.log.2, etc.).
- From the logs directory of the Denodo Monitor that was monitoring that Server, you need to copy the following files and their backup files if they exist:
  - vdp-connections.log
  - vdp-datasources.log
  - vdp-loadcacheprocesses.log
  - vdp-queries.log
  - vdp-resources.log
  - vdp-threads.log
Copy these files to a directory of the host where the Diagnostic & Monitoring Tool runs. The user account that launches the Tool needs to have read access over this directory.
Log in to the Tool.
Create a new server that represents the one from which you obtained the logs. As you do not need to monitor the server, you can only enter the name of the server in the form.
Right-click on the server and click Load Diagnostic Info…
In the Dialog to create a new diagnostic, enter the path to the directory where you copied the logs and click Create. Note that this path has to point to a directory in the host where the web application is running, not a directory on your local host.

Dialog to create a new diagnostic¶

The creation process involves several steps for each log file in the directory: reading logging dates, creating metadata, caching its data and indexing it. According to the size of the log files, creating a diagnostic may be a long process. You can follow its progress in the notification area.

Progress notification of a diagnostic creation¶

If you click on the button, a new notification area will open where you can check the current stage for each individual log file.

Notification of a diagnostic creation with information per file¶

At the end, a new diagnostic will be created in the tree area, under the server, represented with the icon.

New diagnostic node in the tree area¶

Note

The Diagnostic & Monitoring Tool supports partial diagnostics where not all the log files could be loaded into the system. This may happen if the directory does not contain any required files or if the caching failed unexpectedly. If that is the case, those features that rely on missing data will be disabled.

To update a diagnostic with new data, right-click on the diagnostic and click Edit. The Dialog to update a diagnostic will open. If you change the path of the directory with the logs, the current data will be discarded and the diagnostic will use the data from the new folder. On the other hand, if you do not change the path of the directory, the Tool will detect which files have changed and only add data from those files to the diagnostic.

Dialog to update a diagnostic¶

All the diagnostic-related metadata is stored in the same database of the Diagnostic & Monitoring Virtual DataPort. The first time you create a diagnostic, the Diagnostic & Monitoring Tool tries to create this database with the name diagnostic. If the database already exists, the Confirmation dialog of the diagnostic database name will appear, asking for a new database name. Change the database name if you want and confirm. The Tool will use the database you enter in this dialog even if it already exists.

Confirmation dialog of the diagnostic database name¶

USER MANUALS

Creating Diagnostics¶