In the Logs & Alerts tab, the JetPatch Manager Console displays audit and event logs from the JetPatch Manager Console and from managed agents about user and system events, errors, resource levels, and throttling and watchdog actions:
You can manage the table. For example, you can filter the list by Type:
If JetPatch Manager support needs more details about an event, you may be requested to send them the text that appears when you click under Details, or to access other log formats from the Actions menu.
You can view logs relevant to an individual endpoint, from the Servers tab, by clicking its name (in the Name column) and then going to the Logs tab:
To view detailed logs from the connector on a specified endpoint, in the Servers tab, click on a machine's name in the Name column and click View Intigua Logs (to then browse among log files) or Download Intigua Log Package (to download all files, in a zip archive).
JetPatch Manager includes two mechanisms for log quota control:
- For regular logs: These are the logs described above. When the number of logs exceeds 80,000 (you can configure this quota), 10% of the logs (the older ones) are deleted.
- For debug logs: These logs are for use by JetPatch Agent Manager support, and are saved in /tomcat/logs/ , in up to 10 files of up to 10 MB each. When a tenth file reaches 10 MB, the oldest file is deleted and a new file is started.
Notable Logs & Alerts
JetPatch provides many different logs related to all JetPatch components. The logs & alert in JetPatch can be divided into two groups:
- Operational - writes operational activities.
- Agent Management activities like deploying new agents, stop agents, reconfigure agents, and more.
- Patch Management activities like creating Remediation Plans, plan status transitions, collecting updates from the endpoint, and more.
- Platform operations activities like running automation tasks on endpoints, endpoint connection changes, and other general activities related to the endpoint in JetPatch.
- System Audit - writes audit information like login of a new user (including failure attempts), creation/deletion of a user, and system configuration changes.