Alerting on Non-triggered jobs
We recently experienced an issue where Full (and differential) backups were no longer running for an availability group, but log backups were running fine.
The issue in this case was that no backup jobs were triggered against the primary node, which is where full and differential backups are taken.
The way that Azure Backup of availability groups work today, the full backup job is started against all nodes, but fails for all secondaries.
If there was some way to alert on "all nodes failed" or otherwise detect a non-triggering job, that would be appreciated.