Configure and review system logs

Learn how to set the system log level and timestamp format, open the diagnostic log page, and review log data in the Edge Portal.

+ More

Use the Logs section to control which system messages are written, set the timestamp format, and open the diagnostic log page. System logs help you investigate communication problems, configuration errors, service restarts, and unexpected gateway behavior.

System diagnostic logs are different from item historical data and notification history. Logs record software activity. Item history contains stored process values, while notification history records detected conditions and their lifecycle.

Open the log settings

Sign in to the Edge Portal.
Expand Configuration in the sidebar.
Select System.
Expand Logs if the section is collapsed.

The section shows the current Log level and Time format. If either setting is empty or unavailable, the portal displays N/A. An unrecognized log-level value is displayed as Unknown.

Change a log setting

Find Log level or Time format.
Select its edit button, or double-click the setting row.
Select a log level or enter the time format.
Select the check button to save the change.
Confirm that the editor closes and the updated value appears.

Select the cancel button to discard the value you entered.

When you save either log setting, the Edge Portal also requests a restart of the SIA Connect service so the new logging configuration can be applied. The Logs section does not display a separate restart confirmation.

Choose a log level

The selected level is the minimum severity written to the logs. Each level also includes messages with a higher severity.

Log level	Messages included	When to use it
Debug	Debug, Info, Warning, Error, and Fatal	Use temporarily when you need the most detailed technical information. The Edge Portal displays Running in debug mode. as a warning while this level is active.
Info	Info, Warning, Error, and Fatal	Use for general operational activity together with warnings and failures.
Warning	Warning, Error, and Fatal	Use when you only need potential problems and failures.
Error	Error and Fatal	Use when you only need errors that affect functions and critical failures.
Fatal	Fatal	Use when you only need the most critical failures.

Use Debug only for the period needed to reproduce and investigate a problem. Return to the previous level after collecting the required information.

Change the log time format

Time format controls how timestamps are written in log entries.

Edit Time format.
Enter the required timestamp format.
Select the check button.
Open the logs after the service restarts and confirm that new entries use the expected timestamp format.

The Edge Portal provides a text field but does not show format examples or field-specific validation. Keep the current value unless you know the format required by the SIA Connect software version in use.

Changing the time format does not change the gateway clock or time zone. See Manage system settings and time to change those settings.

Open the diagnostic logs

In the Logs section, select View logs.
Review Logs Login Details.
Wait for the password to load.
Select Open logs.

The log page uses these unit credentials:

Field	Value
Username	`admin`
Password	The unit PIN retrieved by the Edge Portal

The portal attempts to authenticate automatically and opens the logs in a new browser tab. If automatic sign-in is unavailable, enter the displayed username and password when the log page asks for credentials.

Allow the Edge Portal to open pop-ups or new tabs. The log page cannot open if the browser blocks the new tab.

Review log data

Record the time when the problem occurred.
Open the log page and start with siacore.log for general SIA Connect activity.
Find entries from shortly before and after the recorded time.
Check the severity and read the complete message.
Look for the affected Connector, instance, item, mapping, address, or service name.
Review nearby entries in sequence. An earlier warning or connection failure can explain a later error.
Copy the relevant entries and their timestamps when contacting support.

The files available on the log page depend on the services installed on the unit. Common log sources include:

Log source	What to review
`siacore.log`	Core operations, Connector activity, data processing, and system events. Start here for most troubleshooting.
Shadow API logs	Shadow API operation and related API or cloud communication.
Watchdog logs	Monitoring of internal process health and service restarts.
Updater logs	Software update activity and update failures.

If the issue concerns a specific Connector or connected system, combine the log message with the resource's event history and current status in the Edge Portal.

Collect useful troubleshooting information

When possible, collect the following information before contacting support:

The system time when the problem occurred
The selected log level
The complete error and the entries immediately before it
The affected Connector, instance, item, mapping, or service name
The action that caused the problem
Whether the problem can be reproduced
The gateway UUID and installed software versions from Workspace > Overview

Troubleshoot log settings and access

Message or condition	What to do
Loading log settings... remains displayed	Reload the page and check that the Edge Portal can communicate with the SIA Connect API.
The setting editor remains open after saving	The setting or service-restart request may not have completed. Check the value, try saving again, and resolve any gateway communication warning.
Unknown is shown for Log level	The API returned a value that does not match Debug, Info, Warning, Error, or Fatal. Edit the field and select a supported level.
PIN code unavailable	The portal could not retrieve the unit PIN. Reload the page and confirm that the system settings API is available.
Allow pop-ups to open the logs page.	Allow pop-ups or new tabs for the Edge Portal, then select Open logs again.
Automatic log sign-in was unavailable. Use the displayed credentials if prompted.	Enter username `admin` and the displayed unit PIN on the log page.
The log page rejects the credentials	Return to the Edge Portal, reopen Logs Login Details, and use the current PIN. Confirm that the PIN has not changed.
The expected message is missing	Check the selected minimum log level. Temporarily select a more detailed level, reproduce the issue, and review the new entries.

diagnostic logs edge portal log level system logs time format troubleshooting

Contact Us