Logging

The MCM component generates log files which can provide extra information when you troubleshoot an issue.

Log file locations

The following table shows the location of various MCM logs that are stored in your Windows and Linux systems.
ComponentWindowsLinux
Plugin Portal log (Configurable through _BESPluginPortal_HTTPServer _LogFilePath)C:\Program Files (x86)\BigFix Enterprise\BES Plugin Portal\BESPluginPortal.log/var/log/BESPluginPortal.log
Windows MDM PluginC:\Program Files (x86)\BigFix Enterprise\BES Plugin Portal\Plugins\WindowsMDMPlugin\Logs/var/opt/BESPluginPortal/Plugins/WindowsMDMPlugin/Logs
Apple MDM PluginC:\Program Files (x86)\BigFix Enterprise\BES Plugin Portal\Plugins\AppleMDMPlugin\Logs/var/opt/BESPluginPortal/Plugins/AppleMDMPlugin/Logs
Windows MDM ServerN/A/var/opt/BESUEM/windows/logs/windowsmdm.log
Apple MDM ServerN/A/var/opt/BESUEM/apple/logs/micromdm.log
Apple MDM GatewayN/A/var/opt/BESUEM/apple/logs/mdmgateway.log 
Apple MDM WebhookN/A/var/opt/BESUEM/apple/logs/mdmwebhook.log 
Android MDM Plugin C:\Program Files (x86)\BigFix Enterprise\BES Plugin Portal\Plugins\AndroidMDMPlugin\Logs /var/opt/BESPluginPortal/Plugins/AndroidMDMPlugin/Logs
Android MDM Server N/A /var/opt/BESUEM/windows/logs/androidmdm.log
WebUI log (Configurable through the server setting _WebUI_Logging_LogPath)c:\Program Files (x86)\BigFix Enterprise\BESWebUI\WebUI\logs\/var/opt/BESWebUI/WebUI/logs/

Client settings - Verbose Logs for Plugin or Plugin Portal

Parameter Description
_BESPluginPortal_Log_Verbose Sets the Plugin Portal Verbose to Off if the value is 0 (only critical messages are logged); sets it to On (to enable more logging) if the value is 1. The default value is 0.
_BESPluginPortal_Log_EnabledLogs When Plugin Portal Verbose is enabled, sets the Plugin Portal message type configuration. Possible values include: all, critical, debug, timing, events. You can add values delimited by semicolons.
Example:
_BESPluginPortal_Log_Verbose = 1
_BESPluginPortal_Log_EnabledLogs = events;timing
The default message type is '“all”.
Note: This can have a detrimental impact on Plugin Portal performance.
_WindowsMDMPlugin_LogVerbose Sets the Windows MDM Plugin Verbose On if the value is 1 and sets Off if the value is 0. The default value is 0.
_AppleMDMPlugin_LogVerbose Sets the Apple Plugin Verbose On if the value is 1 and sets Off if the value is 0. The default value is 0.
_AndroidMDMPlugin_LogVerbose Sets the Android Plugin Verbose On if the value is 1 and sets Off if the value is 0. The default value is 0.

Logrotate

Logrotate handles the automatic rotation and compression of log files to manage available disk space. On the 0th minute of every hour, log files are rotated, and old log files are compressed and kept as backup by running cron jobs in the following containers:

  • windowsmdm
  • applemdm
  • rabbitmq
  • openresty

The backup file name format is <Filename.log>_<YYYY-MM-DD>_<HH-mm-ss>.gz. For example, mdmgateway.log_2020-06-03_07-13-00.gz

Logs are rotated under the following conditions and backed up to the following log locations.

Container Log location Max File size Rotate Count Scheduled cron JOB running
For all containers Container’s internal path 10 MB 10 every hour 0th minute
For macmdm log /var/opt/BESUEM/mac/logs 50 MB 10 every hour 0th minute
For windowsmdm log /var/opt/BESUEM/windows/logs 50 MB 10 every hour 0th minute
For openresty log /var/opt/BESUEM/openresty/logs 50 MB 10 every hour 0th minute
Note: If log file size is less than 50 MB, running the logrotate cron job does not create a new log file.

MCM Debug Logging

Debug logs can help you troubleshoot issues because these logs have an extended logging level. In the BESUEM site, look for Fixlets that are marked as TROUBLESHOOTING to enable logging on different MDM components; they are relevant if you have the components available.