How to troubleshoot when Skedler Alert is not triggered

1. Check whether the Skedler Alerts license is activated.

• Click the About icon in Skedler Alerts Homepage.

• Click License information.

• The License Activation page is displayed.

• Check whether the required values in the Name, Email, Company, and the product key in the License key field.

• Read and select I agree to the terms and conditions checkbox.

• Click Online Activation to activate the Skedler Alerts Product License.

2. Check the alert log to see if the alert was triggered as per the schedule. If not, an empty alert triggered message will be shown in the log.

1. Go to Skedler Alerts UI.

2. Navigate to settings tab, and select debug mode, by default, the value is set as false. You can modify the value as true and click the Save icon.

Location of the log files

Once you have turned the debug mode, reproduce the issue and collect the log files from the following location,

You can find the log files in:

• For Linux/Windows : Skedler Alerts log files in alert_home/log/ directory.  Look for alert.log and alert-elasticsearch.log

• For Debian/RPM in /var/log/skedler-alerts/ directory.

• For Docker in /var/lib/docker/volumes/alertdata/_data/log directory.

3. Test the alert query to see if the query returns any result 

• In the Alert Details page, click on the Test Query – will test the given filters and generate a response.  If the response is empty, then correct your query filters.

• Check whether you can see a result set based on the test query

If the value is available based on the condition, it confirms that the condition is satisfied and the alert will be triggered via email/webhook

4.    Check whether Elasticsearch is running and connected to Skedler Alerts

• Go to Elasticsearch URL and check whether your ELK is running, if not check Skedler log for alert message “No living connections”