Post reply

How Are you checking that your mail notifications are not sending?

  • April 21, 2016 at 2:37 pm

    #325863

    all my jobs on all servers are set to send an email on failure; some jobs have send an email on success too, as that can be relevant.

    i was checking a server, and saw some jobs that had failed, but i did not get an email about the job failing;

    i checked the FailMail view i create on every server, and saw the mails never made it out. they errored out, and the reason's not even relevant here. the issue is when mail fails, how do i get an email saying the mail is not working? hehe.

    So, i'm adding a scheduled task on my local machine to poll all my servers now, and that will open a html report if i'm logged on.

    but how do YOU do the same?

    how do you check that your notification system of choice is not notifying you?

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • April 25, 2016 at 10:35 am

    #1874305

    I created a secondary mail profile connected to a GMail account, and used that profile to send an email notification about any email errors that have occurred.

  • April 25, 2016 at 10:41 am

    #1874307

    I also have a daily job failure summary, that lists all job failures in the last 24 hours. This helps catch any jobs that failed without properly configured notification settings, and occasionally email notification issues if the problem has resolved itself since.

  • April 26, 2016 at 3:13 am

    #1874477

    Maybe a bit extreme but one DBA monitoring team I worked with had a job on every server to log an error every hour. Had a bit of an event storm every hour on the hour, but at lest they knew it was working. This was put in place after the monitoring system fell over and no-one noticed for a few days and then something on one of the SQL server broke.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply