Xibo Log Information
- Xibo for Android
- Install a White Label or a different Player version on a DSCS9
- CEC Screen Power on/off with DSDevices DSCS9
- Hardware Recommendations (website?)
- Philips Signage SoC Monitors (website?
- Managing Storage on the Android Device
- Player Settings
- Players without an Internet Connection
- Remote Administration with SS Helper
- Restart Rooted Device with a Shell Command
- Rooting a Device
- Running Xibo for Android
- Resolving Common Issues
- Error shown when I try to licence my Player?
- Player not updating from the CMS?
- I can see my Licence entry but the Player appears unlicensed?
- Error message - Player is missing dependencies
- My scheduled Layouts are not working?
- Layout won't play? Splash screen plays?
- Watchdog error message
- Troubleshooting for Administrators
- Audit Trail
- Log Information
- Player Logs
- Getting the Player Status
- Can I use the Xibo name / logo?
- Can I run a Xibo Player on Raspberry Pi?
- How can I increase the upload file size limit?
- How do Players communicate with the CMS?
- How many displays can Xibo support?
- How do I reset the Xibo_admin account password?
- Power On/Off for Players
- Why do I need a Default Layout?
- Xibo for Android FAQ's
- Autoplaying Embedded Youtube Videos
- Closing to Home screen
- Displaying Images
- Embedded TV
- External SD card not listed when running Banana-Pi
- Helper Command to change Time zone
- HTML5 Video
- Memory Notifications
- Menu not accessible
- Orientation Settings for the DSDevices DSCS9 Player
- SSL Support
- Using Portrait Displays
- Video wont play properly
On this page
Xibo Log Information
The CMS has a central repository for all Log information, including the Players which send back Log information with each collection from the CMS.
The Log is split into Channels, Functions and Pages for easy searching. Each unique request has a runNo to group messages together.
The Log page is located under the Advanced section of the Menu.
|ID||A sequential ID of log messages|
|Run||The run identifier used to group messages generated by a single request|
|Date||The CMS date of the message|
|Channel||The Channel that the message relates to.|
|Function||The HTTP verb used in the request the generated the message, GET, POST, PUT, DELETE, HEAD.|
|Level||The severity of log message|
|Display||The display name, if the log message came from a Player|
|Page||The page requested - usually the route|
|Message||The log message|
|WEB||The CMS Web Portal|
|API||The CMS API|
|XMDS||The CMS/Player API (Media Distribution)|
|AUTH||The oauth authorization server for the API|
|CONSOLE||XTR task running|
Understanding the log can be complicated in a busy system and it can often be hard to find messages related to your interest. The log can be filtered for this purpose, it is usually best to start with the Channel, then the Function and finally (if necessary) the Page.
Tip: For example, if an API call to the statistics search function is not working as expected the log can be searched for API, GET and
The default log location is the database which can be viewed from the CMS log page. It may be desirable to log to a different location, depending on your use case.
The CMS supports adding new log handlers that confirm to the PSR log handler format - we recommend Monolog. To add log handlers simply append to the
$logHandlers array in
For example to add a file log handler:
$logHandlers = [new \Monolog\Handler\StreamHandler(PROJECT_ROOT . '/log.txt')];