Subject: Follow-up on Backup-Related Strike Alerts
Hi [Recipient's Name],
I have checked into the issue regarding backup-related strike alerts not appearing. Here are my findings:
- There haven’t been many incoming strike alerts in the DB queue for March.
- The backup queue does have some tickets related to Oracle, which aligns with the expected logic, as those specific errors should generate tickets in their queue.
- However, there are several databases that did not generate incidents automatically. Upon checking in BigPanda, I couldn’t find associated alerts for these databases.
Before we request the backup team to investigate further, we need a second round of checks to confirm our findings. Below is the list of databases that did not create incidents, but for which the backup team manually created incidents:
[List of Databases]
Let me know how you’d like to proceed.
Best,
[Your Name]
0 comments:
Post a Comment