Logging

You can view the list of directories that are generated by scanner, notifier, and replay.

Table 1 lists the directories that are generated on start-up by the Scanner, Notifier, and Replay.

Table 1. List of directories generated by scanner, notifier, and replay
Directory	Description
For IBM Data Cataloging: `/opt/ibm/metaocean/data/connections/cos/replay/output/data`	Contains .log files (Kafka messages), stats files and debug information for each scanned vault.
For IBM Data Cataloging: `/opt/ibm/metaocean/data/connections/cos/replay/output/debug/[scanner\|replay]/`	Contains Scanner and Replay debug or troubleshooting information. A new subdirectory is created each time the Scanner and Replay starts. Each subdirectory contains a copy of the configuration file and scanner.debug (replay.debug).
For IBM Data Cataloging: `/opt/ibm/metaocean/data/connections/cos/replay/output/debug/notifier`	Contains Notifier debug or troubleshooting information. A new subdirectory is created each time the Notifier starts. It contains a copy of the configuration file and notifier.debug. Same directory-naming convention as shown for the scanner. The notifier.debug rolls over when it reaches a predefined size as defined in the configuration file. See Configuration file.
For IBM Data Cataloging: `/opt/ibm/metaocean/data/connections/cos/replay/output/archive/`	Contains all .log files that are successfully processed by the Notifier, and their contents are successfully submitted to the Kafka cluster. Remember: Files in this directory are truncated – they contain only the object key and they can also contain the version.
For IBM Data Cataloging: `/opt/ibm/metaocean/data/connections/cos/replay/output/error/`	Contains any .log files that failed to submit to the Kafka cluster.
For IBM Data Cataloging: `/opt/ibm/metaocean/data/connections/cos/replay/output/notification_log/`	The notification.log file contains details of any errors (including stack trace) that occur when it attempts to send notifications to the Kafka cluster. If `logging/notification_log_all` is true in the config file, all successful sends are also logged. The notification.log file rolls over when it reaches a predefined size as defined in the configuration file. See Configuration file.