Topic
This article describes the log files that NinjaOne components generate, where those files are located on managed endpoints, and how to collect them for troubleshooting purposes.
Environment
- NinjaOne Endpoint Management
- NinjaOne Mobile Device Management (MDM)
- NinjaOne Remote and Quick Connect
- NinjaOne OS Deployment
Description
After installation, NinjaOne components generate log files that record operational activity, errors, and diagnostic data for the services running on managed endpoints. When you encounter an issue, knowing where to find these files and how to collect them increases resolution speed and accuracy. This article consolidates log file locations for the NinjaOne agent and related components across supported operating systems.
Select a topic to continue:
Log File Locations
NinjaOne Agent
The NinjaOne agent writes log files to fixed locations on each supported operating system. The following table lists the log file locations by platform.
| Operating System | Log File Location |
|---|---|
| Microsoft Windows | C:ProgramDataNinjaRMMAgent |
| Apple macOS | /Applications/NinjaRMMAgent/programdata |
| Linux | /opt/NinjaRMMAgent/programdata/logs |
Windows
The following table describes the key log files found in the Windows directory.
| File | Contents |
|---|---|
NinjaRMMAgent_<date>_<time>.txt | This file records ongoing agent activity, including executed tasks, triggered conditions, installation events, and communications between the agent and NinjaOne servers. A new file is created each day or when the agent restarts. The 14 most recent files are retained. |
NinjaRMMPatcher_<date>_<time>.txt | The patcher log records activity related to agent version updates and upgrade failures. |
NinjaRMMSignal_<date>_<time>.txt | The agent writes distress signals to this file when it detects a potential problem, such as a crash or loss of connectivity. |
njlink_<xxxxx>_<date-time>.log | This log captures Cloud RDP connection activity. |
jsonoutput-agent.txt | This file contains hardware and software inventory data collected from the device and sent to NinjaOne servers, including OS details, installed software, network adapters, running services, and storage configuration. |
jsonoutput-output.json | NinjaOne uses this file to track the current pending, approved, and rejected OS patches on the device. |
jsonoutput-hist-output-xxx.json | This file records OS patches that have been installed on the device. |
jsonoutput-softwarepatchrecords2.json | NinjaOne uses this file to track the current pending, approved, and rejected third-party software patches on the device. |
jsonoutput-softwarepatch_history_2.json | This file records third-party software patches that have been installed on the device. |
policyagent.config.*.json | These files store the policy settings applied to the device locally, covering areas such as patch management, antivirus, conditions, scheduled automations, and backup. |
appevents.txt | This file contains the 500 most recent events from the Windows Application Event Log. |
sysevents.txt | The System Event Log export contains the 500 most recent system events. |
secevents.txt | The Security Event Log export contains the 500 most recent security events. |
macOS
programdata folder is hidden by default. To reveal it, press Shift + Command + Period. If that shortcut does not work, run the following command in a Terminal session: defaults write com.apple.Finder AppleShowAllFiles trueThe macOS programdata directory is organized into the following subfolders.
| Subfolder | Contents |
|---|---|
| Logs | Agent activity logs (NinjaRMMAgent_<date>_<time>.txt) and patcher logs (NinjaRMMPatcher_<date>_<time>.txt). |
| Jsonoutput | Hardware and software inventory data collected from the device and sent to NinjaOne servers, along with patch records. |
| Jsoninput | Records of scheduled automations and tasks sent to the device. |
| Policy | Configuration files representing the policy settings applied to the device locally. |
| Patch | Patch-related output files. |
Linux
The /opt/NinjaRMMAgent/programdata directory is organized into the following subfolders.
| Subfolder | Contents |
|---|---|
| Logs | Agent activity logs (NinjaRMMAgent_<date>_<time>.txt) and patcher logs (NinjaRMMPatcher_<date>_<time>.txt). |
| Jsonoutput | Hardware and software inventory data collected from the device and sent to NinjaOne servers, along with patch records. |
| Policy | Configuration files representing the policy settings applied to the device locally. |
NinjaOne Mobile Device Management (MDM)
In the NinjaOne MDM Assist app, tap the NinjaOne logo 7-9 times rapidly. The app will enter QA mode. Click the Network logs button, which will appear at the base of the screen. The app will display the logs in plain text. Click the Export logs button to export the logs to a sharing application.
NinjaOne Remote
NinjaOne Remote generates log files for its streaming and playback components. The following table lists the log file locations by operating system.
| OS | Log File Location |
|---|---|
| Windows |
|
| macOS | NCstreamer and NCplayer: Navigate to /Applications/NinjaRemote/logs NCPlayer. From there, navigate to the location stored in the $TMPDIR environment variable. (For example: /var/folders/v1/<<temp_folder_name>>/T) |
| Linux |
|
Quick Connect
NinjaOne Quick Connect writes log files to the following locations on Windows and macOS endpoints:
| Operating System | Log File Location |
|---|---|
| Windows | C:UsersPublicNinjaOneLLCQClogs |
| macOS | Users/Shared/NinjaRMM |
OS Deployment
NinjaOne OS Deployment writes log files to the following location on Windows endpoints: C:ProgramDataNinjaOSDeploy
Collecting NinjaOne Agent Log Files
You can collect NinjaOne agent log files using the methods described below. The collection method differs by operating system.
Windows
To collect log files on a Windows endpoint, run the following command in an elevated command prompt. Replace [OrganizationName-Version] with the organization name and version number from your agent installation folder.
C:Program Files (x86)[OrganizationName-Version]ninjarmmagent.exe /collectlogsAlternatively, if your agent is installed in the default location, run:
C:Program Files (x86)Ninjaoneninjarmmagent.exe /collectlogsThese commands instruct NinjaOne to save the collected log file to the following location:
C:WindowsTempninjalogs.cabmacOS
To collect log files on a macOS endpoint, zip the following folders from the NinjaRMM Agent → Programdata directory and send them to your support contact:
- Logs
- Policy
- Jsonoutput
- Jsoninput
- Patch
Linux
To collect log files on a Linux endpoint, zip the following folders from the /opt/NinjaRMMAgent/programdata directory and send them to your support contact:
- Logs
- Policy
- Jsonoutput