Prerequisites for Monitoring Cron Jobs
Before configuring Cron job monitoring, ensure the following prerequisites are met:
cURL must be installed on the remote Linux machine.
The script linked to the Cron job must have executable permissions.
The machine where Applications Manager is installed should be reachable from the remote Linux machine over the SSL port, without using a proxy server.
The remote machine must have the correct time zone configured and synced.
The Cron job interval must be at least five minutes.
Cron jobs use the HTTPS protocol to send responses to the Applications Manager server and are authenticated using the admin user's REST API key. If the admin API key is regenerated, update the Cron job entry with the new key using the
crontab -ecommand on the remote machine.Linux Cron monitoring is supported only in SSH and Telnet modes.
1. Verify if curl is installed
curl is installed, for example: 2. Ensure the Cron job script has executable permissions
Note: From version 176800 onwards, manual replacement of the <ADMIN_API_KEY> is not required. You can directly copy and paste the generated Cron Job details into the crontab of the remote server. In such cases, you may skip Steps 3 and 4 and proceed directly to Step 5.3. Generate the API key for the Admin user
4. Replace the placeholder in the Cron command
5. Add the Cron job entry on the remote server
- On the remote Linux machine, open a terminal and run crontab -e to edit the user's Cron jobs.
- Paste the updated curl command (with the correct <ADMIN_API_KEY>) into the editor.
- Save and exit.
6. Verify connectivity to the Applications Manager server
If Cron job updates are not reflected in Applications Manager, confirm that the remote server can reach the Applications Manager server and port:
- <remote_server_ip_or_hostname> with the IP address or hostname of the server where Applications Manager is running
- <port_number> with the port number used by Applications Manager (e.g., 9666)
New to ADSelfService Plus?
Related Articles
Prerequisites for monitoring apache server metrics
The Apache mod_status module enables users to view detailed performance metrics of the Apache web server. You must enable and configure the mod_status correctly in the Apache configuration file to get performance metrics from Apache and view the data ...Action Required: Update Cron Job Entries After Version 176800
Starting from Applications Manager version 176800, existing Cron Job entries must be updated to ensure proper monitoring. The updated Cron entry is available under the Curl icon for the Linux Server monitor (in SSH/Telnet mode) in versions above ...Prerequisites - URL Monitoring
Prerequisites: Ensure that the URL you want to monitor is accessible from the machine where Applications Manager is installed. Check if the proxy is configured in Machine/Browser for accessing the URL. If so, the same proxy settings must be ...Monitoring HAProxy - Configuring the HAProxy Stats page
To effectively monitor an HAProxy instance, you can enable and access the HAProxy stats page, which provides real-time metrics about HAProxy's performance. Steps to Enable HAProxy Stats: Open the HAProxy Configuration File: The HAProxy configuration ...Troubleshooting Data Collection Issues in SharePoint Service, Web Applications, Databases and Timer Jobs (MS Office SharePoint monitor - PowerShell Mode)
In MS Office SharePoint monitoring, data for SharePoint Services, Web Applications, Databases, and Timer Jobs is collected using PowerShell. If these metrics are missing, follow the steps below to identify and resolve the issue: 1. Verify the ...