To diagnose what happened in the past in a Virtual DataPort server, follow these steps:
Gather those log files with information about the Virtual DataPort server that you want to diagnose. The Diagnostic & Monitor Tool is able to process the following kind of log files:
From the directory
<DENODO_HOME>/logs/vdp/of the host where the Virtual DataPort server is running, the
vdp.logand its backup files if they exist (by default, its backup files follow the pattern
logsdirectory of the Denodo Monitor that was monitoring that server, the following log files and their backup files if they exist:
server_nameis the name of the Virtual DataPort server in the Denodo Monitor configuration (
Copy these files to a directory of the host where the Diagnostic & Monitoring Tool runs. Note that the user account that launches the Diagnostic & Monitoring Tool needs to have read access over this directory.
Log in to the Diagnostic & Monitoring Tool.
In case you are running the Diagnostic & Monitoring Tool of a Denodo Platform and the server you are diagnosing does not exist in the catalog yet, create it. 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.
If that directory contains log files about several servers, you need to select first which server you want to load the logs from.
The path you specify in this dialog has to point to a directory in the host where the web application is running, not a directory on your local host.
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.
If you click on the button, a new notification area will open where you can check the current stage for each individual log file.
At the end, a new diagnostic will be created in the tree area, under the server, represented with the icon.
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 only contains a subset of all the supported log 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 (or the server name, in case of a directory with logs from several servers), the current data will be discarded and the diagnostic will use the data from the new log files. On the other hand, if you keep the diagnostic definition, the Diagnostic & Monitoring Tool will detect which files have changed and will only add data from those files to the diagnostic.
The Diagnostic & Monitoring Tool of a Denodo Platform stores all its
diagnostic-related metadata in a database of the Virtual DataPort Server of the
same installation. The first time you create a diagnostic, it 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 Diagnostic & Monitoring Tool will use the database you enter in this
dialog even if it already exists.