I have created custom log metric event which filter out failed cronjob and set this custom metric in anomalies detection metric event to monitor failed cronjobs . While setting an alert I have notice that dynatrace is triggering the alert when any job got failed and immediately triggers resolved alert for the same failed jobs . Ideally Cronjob that got failed is already failed and there is no point for dynatrace to trigger resolved status . As since Dynatrace does not offer any default cronjob metric event but still they can add filter in metric event which restrict dynatrace to send resolved trigger for failed cronjob
