Pathfinder Core PRO provides several logging mechanisms and maintains its own internal system logs. The system creates two kinds of log files: System Logs and User Logs.
System Logs are created by the system's internal services and are mainly for troubleshooting with Telos support.
User Logs record the changes on your Axia network that you choose to log for later review.
Click the System > Logs link in the Navigation bar to view the current logs in the system and to define logging options. The page opens on the User Logs. Use the User and System buttons beside the page title to switch between the two.

The page is the list of logs, with a toolbar above it:
the time range button (for example Last 24 h), which applies to everything on the page
a search box, Search every log, and the Search button
Summary, Timeline and Saved searches, which each open in a window over the page
the total number of errors and warnings in the listed logs over the time range, when there are any
Below the list, Delete/Clear All Logs deletes or clears every log in the list after you confirm.
Important Note: The log tools are for administrators. Other users, or any user while the log service is unavailable, see a plain list of log files.
Time Range
Click the time range button to open the time range panel. Pick Last 15 min, Last hour, Last 24 h, Last 7 days or All, or type a from and to time and click Apply. The button then shows the range you chose. All times are the unit's own time (unit time), whatever time zone your browser is in.

The chart in the panel, and the narrower strip above the list, show how many log entries were written over the range. Red marks errors and yellow marks warnings. Click a bar to see that stretch of time on the Timeline. If the bar covers more than two hours, the time range is narrowed to that bar first.
The List of Logs
The list shows every log:
Column | Description |
|---|---|
Log | The Filename of the log. A log that has been rotated shows how many files it has; click the arrow beside it to list them. See Log File Maintenance later in this article. Clicking a log Filename opens the log in a browser. |
Covers | The time of the first and last entries. |
Size | The total size of all the log's files. |
Last updated | The date and time the log was Last Updated. |
Time range (for example Last 24 h) | The number of errors and warnings in the time range, or quiet if there were none. Click one to step through them on the Timeline. |
Each log has a View button and a ⋯ button that opens a menu with Tail, Download and Delete/Clear. When a rotated log is opened with its arrow, each of its files has the same buttons.

View opens the log in a window, as columns (time, writer, operation, object and properties), with warnings and errors colored. Use Older and Newest to move through it, Follow to keep showing new entries as they are written, Open file to open the raw file, Download to save it, and Close to close the viewer.

Tail opens the file that is being written to in the same viewer, with Follow switched on, so new entries appear as they are written. Click Follow again to stop.
Download saves the log. For a rotated log, the files are joined, oldest first, into one download. Each file can also be downloaded on its own from the list of files.
Delete/Clear deletes the log's files, or empties the file that is being written to, after you confirm.
The system logs list looks the same and shows the logs of the system's services and the operating system:

Benign Warnings and Errors
Some warnings and errors are expected on a particular system and are not a sign of trouble, for example a device that is switched off on purpose. In the Search and Timeline windows, click Mark benign beside such an entry. Entries like it are then left out of the warning and error counts, so the counts show what needs attention. Tick Count benign below the list to include them again. Once something has been marked, a Marked benign button beside it lists the marks.
Search
Type a word or phrase in Search every log and click Search. The Search window opens with every entry that contains it, in any log and its rotated files, within the time range. Click Search with the box empty to open the window and build a search there. Clicking the error or warning total in the toolbar lists those entries in the same window.

Choose Contains or Does not contain, type the text, and choose how it is matched: anywhere in the entry, as a whole word, or as a regular expression. Tick Match case to match upper and lower case exactly.
Click + Add criterion to add more terms, and choose whether Entries must match all of the included terms or any of them.
Show limits the results to errors, warnings and information entries.
In: narrows the search to particular logs. By default, every user and system log is searched.
Context shows none, 1 or 3 entries before and after each match.
Click Search. Each match shows the log it is in, with View in log to open the viewer at that entry and Around this time to open the Timeline at that moment. When there are more matches than are shown, a button at the bottom shows the next set. Click Export .txt to save the results as a text file, and Close to return to the list.
Saved Searches
Click Save search… in the Search window to keep a search for later.

Click Saved searches in the toolbar to list them, with the number of new matches since each was last viewed. The same number appears on the Saved searches button whenever the Logs page opens, so a saved search works as a simple watch for a problem coming back.

Click Run to run a search again, Rename… to rename it, or Delete to remove it. Saved searches are shared by everyone who uses the Logs page.
Summary
Click Summary in the toolbar to summarize the logs over the time range. Pick All logs, User logs or System logs and click Summarize.

The summary shows the number of entries, warnings, errors, and starts and restarts of the system's services, followed by:
Most repeated warnings and errors, grouped by message, with Find to search for them and Timeline to see when they happened
Devices that dropped, REST endpoints failing, and Starts and restarts
Click Download support bundle to save a ZIP file to send to Telos support. It holds the logs cut to the time range, the summary, and a description of the unit. Keys in REST addresses are removed from it.
Timeline
Click Timeline in the toolbar to see every log's entries around a moment. Pick a time in Around, how far either side to look (for example ± 5 min), and which logs, then click Show. You can also get here from Around this time on a search result, by clicking a bar of the chart, or by clicking a log's error or warning count.

Each log is a lane, with a mark for each entry: blue for information, yellow for warnings and red for errors. Below the lanes, the entries are listed in time order. Click or drag on a lane to move the orange line; the Around time follows it. When you arrive from an error or warning count, Previous and Next step through those entries one at a time.
Creating New Log Writers
To see the list of Log Writers that have been created in the system, click the Log Writers link on the Logs page.

This page lists each Log Writer in the system by Name, along with its type and location.
To create a new Log Writer, click Add + on the Log Writers screen.

Type a Name for this Log Writer in the Log Writer Name field.
From the Log Writer Type drop-down list, select this Log Writer’s Type. You can create four types of Log Writer:
Log Writer Type | Description |
|---|---|
Log File | Stored locally on the Pathfinder Core PRO system, these logs are subject to regular rotation, deletion, and cleanup depending on space requirements. This Log File Type is useful for logging recent events but should not be relied upon for long-term storage. |
TCP Listener | This type of Log Writer listens on a TCP port and sends the log entries as plain text messages to any application that connects. For example, you could use a PuTTY (telnet) session to connect to the system and monitor log changes dynamically. |
TCP Client | This type of Log Writer attempts to connect to an IP address and port and, if it connects, sends the log messages as plain text messages to the listening application. |
Syslog | This is the recommended method for long-term log storage. Syslog is a widely used standard protocol for log collection, viewing, and storage used by many systems and IT scenarios. A number of syslog collection applications exist, both freeware and commercial. A quick internet search should provide you with a variety of options. |
Fill in the fields for the type you chose:
Type | Fields |
|---|---|
Log File | None. The file is named after the Log Writer, with .log added. |
TCP Listener | Type the Port associated with the TCP application. Also set Max Offline Cache Count (how many entries, 1–5000, are kept for an application that connects later) and Connect Get Requests. |
TCP Client | Type the IP Address and Port associated with the TCP application. Also set Max Offline Cache Count and Connect Get Requests. |
Syslog | Type the IP Address of the collector application. |
Tick Skip Web Client SapV2 to leave out the SapV2 messages exchanged between the web pages and the system itself (from 127.0.0.1). This option only matters when a SapV2 option under MessageLogging is ticked. It limits that log to traffic from outside applications.
Use the selection window at the bottom of this dialog to select what to log. Expand the tree and tick the items you want to log.
The available items are listed below. The number beside each is its message type id, which appears in every log entry it writes (see Log Message Structure).
Group | Item (id) | What it logs |
|---|---|---|
AudioAlarms | AlarmState (3001) | Generates a log message whenever an audio alarm state changes. |
AudioAlarms | LvlState (3002) | Generates a log message whenever the audio threshold for silence is passed for longer than 250 ms. This occurs before the countdown to an alarm state begins. It can be used to log the actual transitions being reported by the equipment but may also generate a large amount of log content depending on the type of audio content being monitored. |
Clustering | ConsolidatedNodeStates (15001), IsPrimaryActive (15002), AllNodesAttempted (15003), SyncProgress (15004), NodeState (15005), EventSystemIsPrimary (15006), Online (15007) | Changes to the cluster's state and each node's state. |
ConnectMessage | Connected (1001) | Logs connections and disconnections from equipment. Use this log message to find equipment with which Pathfinder Core PRO is struggling to maintain a connection. |
ConnectMessage | Online (1002) | Logs changes to the online/offline state of the device. For a device to be considered online, proper communications must be occurring on all identified ports. |
ConnectMessage | LoginState (1003), LastConnectionState (1004) | A device's login state, and the reason its connection last changed. |
Custom | (80001–99999) | Any custom SapV2 subscriptions that have been defined through the Add Custom button. Each must have a Name, an unused Log Type Id between 80001 and 99999, a Log Severity (Emergency, Alert, Critical, Error, Warning, Notice, Informational or Debug), and a valid SapV2 subscription message. |
DeviceEmulators | ConnectedCount (11001), Connected (11002) | Connections to device emulators. |
DeviceEmulators | WatcherTriggered (11003), WatcherTriggeredValue (11004) | Watchers that trigger, and the value that triggered them. |
DeviceEmulators | LastSent (11005), LastReceived (11006), GenericEmulatorsLastSent (11007), GenericEmulatorsLastReceived (11008), ProbelEmulatorsLastSent (11009), ProbelEmulatorsLastReceived (11010) | What emulators send and receive: all emulators, or only generic or only Probel ones. |
DeviceEmulators | ProbelEmulatorsRouteChangeRequestReceived (11011) | Route change requests received by Probel emulators. |
Devices | VMIXState (7001), VMIXGain (7002) | Logs changes to VMIXer On/Off settings and VMIXer gain settings. |
LegacyPanels | PanelPropertyChanged (5001) | Logs changes to properties of any of the controls in user panels. |
LogicFlows | TranslatorOutputChanged (4001) | Logs changes whenever a logic flow translator changes its output. |
LogicFlows | CombinerOutputChanged (4002) | Logs changes whenever a logic flow combiner changes its output. |
MemorySlots | MemorySlotChanged (6001) | Logs whenever a memory slot changes its value. |
MessageLogging | LwrpIncoming* (9001), LwrpOutgoing* (9002), LwcpIncoming* (9003), LwcpOutgoing* (9004) | Lwrp and Lwcp incoming and outgoing messages. |
MessageLogging | SapV2InternalIncoming* (9005), SapV2InternalOutgoing* (9006) | Incoming and outgoing SapV2 messages between services. |
MessageLogging | SapV2ExternalIncoming* (9007), SapV2ExternalOutgoing* (9008) | SapV2 messages coming from outside the system and being sent outside of the system. |
MessageLogging | LoginFailures (9009), LoginSuccesses (9010), AccessViolations (9011) | Logins, and attempts to use something the user has no rights to. |
MessageLogging | AuditGet (9012) | Logs incoming SapV2 messages that request information, for security audit purposes. |
MessageLogging | AuditSet (9013) | Logs incoming SapV2 messages that request changes, for security audit purposes. |
RestApi | LastSent (12001), ResponseData (12002), ResponseCode (12003), ResponseSuccess (12004) | Requests sent to REST API devices and their responses. |
RouterEvents | RouteState (2001) | Logs any route changes that take place within the system. |
RouterEvents | Gpio State (2002) | Logs changes to GPIOs within the system. |
SapPropertyRouter | DestinationMessageBeingSent (13001) | Messages sent to SAP property router destinations. |
Scenes | SceneIsActive (14001), SceneState (14002), ActivateSceneRequested (14003), ItemsAreActive (14004), ItemsCurrentValue (14005) | Scene activations and the state of their items. |
Scte35 | 10001–10025 | SCTE-35 cue messages received and triggered, their fields, and the state of the SCTE-35 reader. |
TimeEvents | Elapsed (8001) | Logs whenever timers elapse. |
TimeEvents | Enabled (8002) | Logs changes to a timer's enabled state. |
Items marked with an asterisk (all in MessageLogging) should be used with support or when trying to find a problem, as these can increase CPU load. These are for troubleshooting only.
When all fields are complete, click Apply to save your changes and create the Log Writer.
Log File Maintenance
You may notice that some logs have multiple copies with a period and a number at the end. The list shows these together under one log.
Because space is limited, Pathfinder Core PRO runs a log rotation service that rotates the log files when they become too large: the current file is renamed with .1 added, older files move up one number, and the oldest is deleted.
This service also has rules that may rotate or delete logs more aggressively when space is running low. For this reason, we recommend that you use an outside syslog-based logging service to capture logs that you want to keep for longer. Review the Creating New Log Writers section for additional details.
Log Message Structure
Pathfinder log messages follow one of three formats depending on the log writer options selected and the type of message. If you choose Syslog as the log writer type, then the syslog structure is used. All other writer types use the standard log message structure. If the message type is one of the audit get or audit set message types, the log message data is wrapped in an audit log message structure.
Standard log message structure
By default, log messages are composed of a timestamp, a message type id number, and a sap message:
<TimeStamp> <MessageTypeId> <sap message>
For example:
12-26-2023_11:45:00.001 6001 indi MemorySlots#0.MemorySlot#Time3 SlotValue=FalseTimestamp: Date and Time structured as: MM-dd-yyyy_HH:mm:ss.fff
MessageTypeId: Each message item in the log writer editor checkboxes has an associated id number (listed above). For example, memory slot value changes have an id of 6001. This allows for easy filtering of specific message types.
Message: Each message is a SapMessage made up of an operator, object path, list of properties, and in some cases a list of system items. For more details on the structure of SapMessages, see Appendix A.
Note: Two spaces are used between the timestamp and the message type id and again between the message type id and the sap message data itself.
Audit log message structure
Audit log messages follow the same format as standard log messages except that the SapMessage wraps the original message with additional data:
01-03-2024_13:59:47.554 9012 indi AuditGet#[tcp://192.168.1.230:41202/] Direction=Incoming, Message="ClusterAdmin:get Devices#0 Ping<CR,LF>"
01-03-2024_13:59:49.230 9012 indi AuditGet#[tcp://192.168.1.230:9600/] Direction=Incoming, Message="<NoUser>:indi Devices#0 Ping=Pong<CR,LF>"An audit log message includes an object path of AuditGet or AuditSet with a URL where the original audit message originated. Typically, the URL begins with either tcp:// or ws:// for a TCP or WebSocket connection, followed by the IP address and port. The Direction property indicates the direction of the message as incoming or outgoing. The message property itself contains the user name used, followed by a colon and the original SapMessage. Outgoing messages may specify <NoUser> as the user since the outgoing message (especially if it is a change message) is not necessarily associated with a specific user. Carriage returns and line feeds in the original message are expressed as <CR,LF>.
Syslog message structure
When syslog is chosen for the log writer in Pathfinder, RFC 3164 format is used, except that Pathfinder's timestamp portion of the message also includes the milliseconds.
<<severity>><timestamp> <localip> PFC: <MessageTypeId> <MessageObjectPath> <PropertyList>
<14>Jan 03 16:15:02.619 192.168.1.96 PFC: 6001 MemorySlots#0.MemorySlot#ttt SlotValue=B
<14>Jan 03 16:22:11.150 192.168.1.96 PFC: 9012 AuditGet#[ws://[::1]:56483/] Direction=Incoming Message="Admin:GET Devices#0 Ping<CR,LF>"A syslog message is made up of a severity calculation followed by a timestamp in the format MMM dd HH:mm:ss.fff (normally RFC 3164 does not include the millisecond portion). Next comes a single space and the message portion, which includes a tag (usually process name) and then the message data. Pathfinder Core PRO uses PFC: as the tag. The message itself is the object path and property list from the SapMessage as described in the standard and audit logging above. The operator and system items from the SapMessage are not included when syslog options are selected.