View Log

1. Overview

This tab allows viewing of two log types:

  • DebugLog – A comprehensive operational log containing all system events, status codes, and operations performed by the Provisioning Portal.

  • CustomLog – A filtered log that includes only entries with specific status codes configured in CustomStatus.xml (see CustomStatus.xml for configuration details).

Both log types are generated daily and contain entries only for operations performed on that day. Logs open in a new browser tab when you click the corresponding link.

1.1. Log Format

Each log entry follows this format:

Host: <hostname>, Date: <DD.MM.YYYY>, Time: <HH:mm:ss>, Value: <message>

Where:

  • Host – The hostname of the server where the Provisioning Portal is running

  • Date – The date when the log entry was created (in DD.MM.YYYY format)

  • Time – The time when the log entry was created (in HH:mm:ss format)

  • Value – The log message, typically including device identifier (Serial Number or MAC address) and status information

1.2. Log File Naming

Log files are stored in Log/ folder with the following naming convention:

  • DebugLog_DD.MM.YYYY.txt – Daily debug log file

  • CustomLog_DD.MM.YYYY.txt – Daily custom log file

Example:

DebugLog_14.10.2025.txt
CustomLog_14.10.2025.txt

2. Functionality and usage

  • View DebugLog – Click the Debug log link to open the full log for the current day. This log contains all provisioning operations, status updates, and system events. Use this log for comprehensive troubleshooting and detailed analysis of provisioning flows.

  • View CustomLog – Click the Custom log link to open the filtered log for the current day. This log contains only entries with status codes specified in CustomStatus.xml configuration file. Use this log for focused monitoring of specific provisioning events without searching through the entire DebugLog.

  • Navigation – Use the browser’s back button or the Back navigation control to return to the previous screen.

3. Use Cases

3.1. When to use DebugLog

Use DebugLog when you need to:

  • Investigate the complete flow of a provisioning operation

  • Troubleshoot unexpected behavior or errors

  • Review all interactions with the ACS (Auto Configuration Server)

  • Audit all system operations for a specific day

  • Analyze the sequence of events leading to an issue

3.2. When to use CustomLog

Use CustomLog when you need to:

  • Monitor specific provisioning statuses (e.g., successful completions)

  • Track critical events without reviewing the entire log

  • Generate reports for specific status codes

  • Focus on particular types of operations (e.g., device found events)

  • Quickly identify occurrences of configured status codes

4. Configuration

The CustomLog filtering is controlled by the CustomStatus.xml configuration file. To add or remove status codes from CustomLog:

  1. Edit the CustomStatus.xml file located in the XML configuration directory

  2. Add or remove <status id="XXX"></status> entries for the desired status codes

  3. Wait up to 10 minutes for automatic reload, or restart the application for immediate effect

For detailed information about CustomStatus.xml configuration, see CustomStatus.xml Configuration.

5. Technical Details

  • Log rotation: Log files are created daily with date-based naming

  • File location: Log/ folder

  • File retention: The application does not automatically delete old log files; implement your own retention policy as needed

  • Thread safety: Log writing is thread-safe using ReentrantLock to prevent concurrent write issues