Diagnostics

You can use Longview Server Manager to open the Diagnostic page. The Diagnostics page allows you to establish and manage logging and tracking activities related to diagnostics and support. The Diagnostics page displays the Diagnostic settings and Diagnostic files tabs. Additionally, there is a link to open the lv_dataserver.log file directly from the Diagnostics page, allowing you to open the file without having to navigate elsewhere when debugging.

To access the Diagnostics page, click the Diagnostics tile under the Functionality section on the Server Manager home page.

Refresh button

At any time, you can click the Refresh button to refresh the Diagnostics page and view an updated value on the Diagnostics Settings tab, especially when someone has changed a value. Refresh will also update the list of diagnostic files on the Diagnostic files tab that have been added or deleted outside the Server Manager.

Search

In each functionality page, you can use the Search field to easily find the items you need. The search filters as you type and applies to all tabs in each page, meaning, when you switch between the tabs in a functionality page, each tab displays only the matched items. To clear the search, remove what you have typed from the Search box.

Diagnostic settings Tab

The Diagnostic settings tab opens by default when you access the Diagnostics page. The page displays various diagnostic settings options. You can select or deselect the check boxes of the parameter to turn specific logging on or off. The diagnostics do not require the servers to be restarted for the parameter changes to take effect.

Saving selected diagnostic settings

The following table lists the parameters that you can configure in the Diagnostics page:

Setting	Default	Description
Enable web trace	Cleared	Enables web trace to assist in debugging web connection problems.
Service tracking	Cleared	Specifies whether to include diagnostic service tracking information in the Longview Data Server Log (lv_dataserver.log). Selected — Includes diagnostic service tracking information. These statistics are included for agents, web agents, and locking, management, and security servers. Cleared — Disables logging of service tracking information.
Service detail	Cleared	Specifies whether to include diagnostic service detail information in the Longview Data Server Log (lv_dataserver.log). Selected — Includes process timing and memory usage information in the Longview Data Server Log. Process timing information includes the elapsed time of a service, the count and sum of elapsed time per unique service, and summarized timing statistics. This information is included for agents, web agents, and locking, management, and security servers. The execution time of an event (from fired to completed) is logged, as well as the wait time between an event being triggered and fired. Cleared — Disables tracking and logging of process timing and memory usage information.
Service logging	Cleared	Specifies whether to track and log service activity information. When this setting is selected, the system generates a separate .csv log file, per agent process, that contains diagnostic service tracking information.
Query statistics	Cleared	Specifies whether to include query statistic information in the Longview Data Server Log (lv_dataserver.log).
Query logging	Cleared	Specifies whether to log query information. When this setting is selected, the system generates a separate .csv log file, per agent process, containing detailed information about all queries.
RDBMS logging	Cleared	Specifies whether to track and log RDBMS information. When this setting is selected, the system generates a separate .csv log file, per agent process, that contains RDBMS activity information.
Event profiling	Cleared	Specifies whether to output event profiling for diagnostic purposes. When this setting is selected, profiling for each event is enabled and output to two files: the profile for each event is output to the profile_EventProc_RuleID.csv file and overwritten each time a rule ID is triggered. the profile for the bottleneck event for each iteration is appended to the profile_criticalpath.csv file. The number of concurrent events (triggered and/or fired) are logged in the lv_dataserver.log file.

Diagnostic files Tab

Click the Diagnostic files tab in the Diagnostics page to view files, open a required file, or delete a file. You may open or delete a diagnostics log file from the Diagnostic files tab.

Opening diagnostic files

To open diagnostic files in the Server Manger, follow these steps:

Open the Diagnostics page. The Diagnostic settings tab opens by default.
Click the Diagnostic files tab. When selected the diagnostic log files are listed on the page.
Click the appropriate diagnostic file name, or the More options menu (ellipsis) in the Actions column of that row and select Open.
The log file opens in a text editor such as Microsoft WordPad. From here, you can read or save the file to your local or network drives.

Deleting diagnostic files

To remove a diagnostic log file, follow these steps:

Open the Diagnostics page. The Diagnostic settings tab opens by default.
Click the Diagnostic files tab. When selected the diagnostic log files are listed on the page.
To delete one or more log files, click the check box on the diagnostic file(s) you want to delete. To delete all log files under the tab, click the check box on the header row of the table and all log files are selected.

Opening Diagnostics Log File

Click the Delete icon which appears on the right side of the tabs. A confirmation dialog opens.
Click Delete to delete the diagnostic file(s).
The selected diagnostic file(s) are deleted, and you receive a toast notification on the success of the deletion process

Note: In some cases, a .csv file cannot be deleted while the servers are running. If the .csv file cannot be deleted, try stopping the servers, and then attempt to delete the file again.