How to enable additional Discovery Logging in DX NetOps Performance Management.
How to enable Discovery debug logging on the Data Collector.
How to enable Discovery debug logging on the Data Aggregator.
Enable Discovery logging with the org.ops4j.pax.logging.cfg file on the Data Collector or Data Aggregator.
How to debug problems where Discovery is failing in Performance Management.
All supported Performance Management releases
To enable the DEBUG level logging we edit the org.ops4j.pax.logging.cfg file and remove comments from debug lines that are already in the file. Disabling the debug is done by adding the comments back in front of the same lines.
The file edited on both the Data Aggregator and Data Collector is located in the following location on each host. Default install home paths are shown.
Both files have a section that looks like this:
Uncomment the lines in the logging file for the Data Aggregator or Data Collector as required or as directed by support. There are instances where logging is only needed from one server and not the other.
To enable the logging on either server open the logging file for editing and remove the '#' comment symbols from the front of all lines in the 'For debugging Discovery issues' section. Save the changes to the file.
When done it should look like this:
After enabling logging and reproducing the issue, disable the logging to halt further log writes. To disable the logging edit the logging file and add the '#' comment characters back to the start of the lines they were removed from. Save the changes.
The logging is written to the Discovery.log file on both Data Aggregator and Data Collector. They are found in these locations. Default install paths are shown.
When attaching the individual logs, please rename them to DA_Discovery.log and DC_Discovery.log. Attaching two files to the case with the same name results in the second file uploaded overwriting the first.
Alternatively run the re.sh script on each host and attach the resulting diagnostics packages to the support case for analysis. The re.sh script instructions are found in the documentation on the Unable to Resolve Issue page.
NOTE: Be sure to disable logging when done reproducing the issue. This logging, if left enabled, can generate a large amount of logging that could fill a disk up and cause an outage.