Editing Training 2022 Linux team/ (section)

==Training session on Nagios Alert 07 Feb 2023 - Tetra Support Staff - Alok==

{{#ev:youtube|J56PqqvexAI|640}}

'''Video summary:''' "Training session on Nagios Alert Tetra Support Staff Alok" -- a focused session on the judgment call behind mail-queue-growth alerts specifically: when a queue-size warning fires but the support engineer on shift doesn't have credentials to log into that particular mail server, the correct move is NOT to guess whether it's normal or a problem -- it's to call the engineer who does have access and ask them to check the actual mail contents. Uses Hero MotoCorp as the running example: it has 3000+ dealer/account recipients, so any single outbound campaign naturally spikes the queue as it fans out to all of them, making a growing queue completely normal there and not something to escalate reflexively. Teaches the actual verification method for engineers who do have access: log into the server and read the queue contents directly to confirm whether messages are genuine business mail or spam, and if genuine, no action is needed even though the count keeps climbing -- but recommends watching the trend for at least 20-30 minutes before concluding it's benign, since a queue that keeps climbing without leveling off is the actual red flag. References a real recent incident as a contrast case: spam sent through one relay mail ID caused a relay server's queue to spike to ~2000+ messages overnight, which was NOT normal and required immediate escalation -- explicitly reasoning that queue growth can't just be assumed harmless, because if it actually is spam, the sending IP risks getting blocklisted by receiving mail providers, which is the real business risk driving the urgency to verify rather than wait.