Prerequisites for Monitoring Cron Jobs
Below is the list of prerequisites for monitoring Cron jobs:
- Curl must be installed in the remote Linux machine.
- Script linked to the cron job must have executable permission.
- The machine where Applications Manager is installed should be reachable from the remote Linux machine via SSL port without any proxy server.
- The remote machine where the cron job is running must be synced with the correct time zone.
- Cron job interval should be a minimum of five minutes.
- Cron job uses HTTPs protocol to send responses to the machine where Applications Manager is installed and is validated using the admin user's Rest API key. If the admin user's API key is regenerated, then update the latest API key for all the cron job(s) on the remote Linux machine using the crontab -e command.
- Linux cron is supported only in SSH and TELNET mode of monitoring.
Steps to configure Cron jobs
1)Check whether curl is installed in the system where cron jobs are running, by executing the below command in terminal
$curl -V
Output should be similar as below
2)Check the script added in the cron job addition is having executable permission
$ls -al <script added in Job script path>
[testuser@test-machine]$ ls -al test.sh
-rwx------. 1 testuser testgroup 35 Apr 24 22:38 test.sh
3)Under Settings -> User Management ->Click on Admin User and generate the API key by clicking the Click here as shown
4)Replace the <ADMIN_API_KEY> with the api key generated above
5)After replacing paste the content in the target server where cron job is running by following the steps below
- In target server terminal execute
$ crontab -e
- A cron editor will open
- Paste the curl content and save and exit
- The terminal should return the following
crontab: installing new crontab
If cron job details are not getting updated in Applications Manager even after performing the above steps , check whether the target server can access the Applications Manager installed machine and the port in which it is running by executing the below command in the target server.
telnet remote_server_ip port_number
remote_server_ip/hostname - Replace remote_server_ip with the hostname/ipaddress of machine in which Applications Manager is running.
port_number - Replace Port number with port number in which Applications Manager is running
Example
http://127.0.0.1:9666 - APM build link
telnet 127.0.0.1 9666
telnet 127.0.0.1 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 ...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 ...What are the prerequisites required to monitor 'Top 10 Queries By CPU' in PostgreSQL monitor?
1. Include the below lines in postgrsql.conf file located in <Data DIRECTORY>: shared_preload_libraries = 'pg_stat_statements' pg_stat_statements.track = all 2. Execute the below commands in psql shell: CREATE EXTENSION pg_stat_statements; 3. Restart ...