MS SQL 监控错误日志的告警信息

SQL Server的错误消息（Error Message）按照消息的严重级别一共划分25个等级，级别越高，表示严重性也越高。但是如果你统计sys.messages,你会发现，实际上只有16（SQL SERVER 2008/2012）或17个（SQL SERVER 2005）个级别。猜测应该是一些留作扩展用，一些留作用户自定义错误消息的级别。

sys.messages中有个字段is_event_logged，取值为1时表示出现错误时将消息记入事件日志。对于 message_id 中的所有消息语言，此参数都是相同的。所以也就是说有些错误信息（Error Message）会写入事件日志，有些就不会写入错误日志。因此监控错误日志时，我们只能监控那些写入错误日志的错误信息。一般而言，我们应该监控严重级别在16~25之间的错误信息，另外严重级别14的也应该监控（主要是Error: 18456, Severity: 14）。

监控错误日志有很多方式，下面介绍一种非常简单、有效的监控错误日志的方法.我们可以通过sp_add_alert创建一个警报（Alerts），如下所示，我们创建一个名称为SQL Server Severity Event 14的警报（配置前需要配置邮件、ProfileName，Operators,下面脚本也要根据具体情况调整）。关于创建警报的具体信息，可以参考http://msdn.microsoft.com/zh-cn/library/ms189531.aspx

USE [msdb]

GO

IF NOT EXISTS(SELECT 1 FROM msdb.dbo.syscategories WHERE NAME='DBA_MONITORING' AND category_class=2)

BEGIN

EXEC msdb.dbo.sp_add_category

    @class=N'ALERT',

    @type=N'NONE',

    @name=N'DBA_MONITORING' ;

END

GO

IF EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'SQL Severity Event 14')

 EXEC msdb.dbo.sp_delete_alert @name=N'SQL Server Severity Event 14'

GO

USE [msdb]

GO

EXEC msdb.dbo.sp_add_alert @name=N'SQL Server Severity Event 14',

  @message_id=0,

  @severity=14,

  @enabled=1,

  @delay_between_responses=60,

  @include_event_description_in=1,

  @category_name=N'DBA_MONITORING',

  @job_id=N'00000000-0000-0000-0000-000000000000'

GO

EXEC msdb.dbo.sp_add_notification @alert_name=N'SQL Server Severity Event 14', @operator_name=N'YourSQLDba_Operator', @notification_method = 1

GO

如下所示，在UAT服务器，我故意用dw账号错误密码登录数据库，一分钟后，我立马回收到一封告警邮件

DATE/TIME: ;        2014/10/28 9:21:42

DESCRIPTION: ;    Login failed for user 'dw'. Reason: Password did not match that for the login provided. [CLIENT: 192.xxx.xxx.xxx]

COMMENT: ;        (None)

JOB ;RUN:              (None)

SQL Server 错误日志

Windows事件日志

我们依次建立16-25级别的告警来监控数据库错误日志的错误信息。如下所示：

IF NOT EXISTS(SELECT 1 FROM msdb.dbo.syscategories WHERE NAME='DBA_MONITORING' AND category_class=2)

BEGIN

EXEC msdb.dbo.sp_add_category

    @class=N'ALERT',

    @type=N'NONE',

    @name=N'DBA_MONITORING' ;

END

GO

IF  EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'SQL Severity Event 16')

    EXEC msdb.dbo.sp_delete_alert @name=N'SQL Server Severity Event 16'

GO

USE [msdb]

GO

EXEC msdb.dbo.sp_add_alert @name=N'SQL Server Severity Event 16',

        @message_id=0,

        @severity=16,

        @enabled=1,

        @delay_between_responses=60,

        @include_event_description_in=1,

        @category_name=N'DBA_MONITORING',

        @job_id=N'00000000-0000-0000-0000-000000000000'

GO

EXEC msdb.dbo.sp_add_notification @alert_name=N'SQL Server Severity Event 16', @operator_name=N'YourSQLDba_Operator', @notification_method = 1

GO

USE [msdb]

GO

IF NOT EXISTS(SELECT 1 FROM msdb.dbo.syscategories WHERE NAME='DBA_MONITORING' AND category_class=2)

BEGIN

EXEC msdb.dbo.sp_add_category

    @class=N'ALERT',

    @type=N'NONE',

    @name=N'DBA_MONITORING' ;

END

GO

IF  EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'SQL Server Severity Event 17')

EXEC msdb.dbo.sp_delete_alert @name=N'SQL Server Severity Event 17'

GO

USE [msdb]

GO

EXEC msdb.dbo.sp_add_alert @name=N'SQL Server Severity Event 17',

        @message_id=0,

        @severity=17,

        @enabled=1,

        @delay_between_responses=60,

        @include_event_description_in=1,

        @category_name=N'DBA_MONITORING',

        @job_id=N'00000000-0000-0000-0000-000000000000'

GO

EXEC msdb.dbo.sp_add_notification @alert_name=N'SQL Server Severity Event 17', @operator_name=N'YourSQLDba_Operator', @notification_method = 1

GO

USE [msdb]

GO

IF NOT EXISTS(SELECT 1 FROM msdb.dbo.syscategories WHERE NAME='DBA_MONITORING' AND category_class=2)

BEGIN

EXEC msdb.dbo.sp_add_category

    @class=N'ALERT',

    @type=N'NONE',

    @name=N'DBA_MONITORING' ;

END

GO

IF  EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'SQL Server Severity Event 18')

    EXEC msdb.dbo.sp_delete_alert @name=N'SQL Server Severity Event 18'

GO

USE [msdb]

GO

EXEC msdb.dbo.sp_add_alert @name=N'SQL Server Severity Event 18',

        @message_id=0,

        @severity=18,

        @enabled=1,

        @delay_between_responses=60,

        @include_event_description_in=1,

        @category_name=N'DBA_MONITORING',

        @job_id=N'00000000-0000-0000-0000-000000000000'

GO

EXEC msdb.dbo.sp_add_notification @alert_name=N'SQL Server Severity Event 18', @operator_name=N'YourSQLDba_Operator', @notification_method = 1

GO

USE [msdb]

GO

IF NOT EXISTS(SELECT 1 FROM msdb.dbo.syscategories WHERE NAME='DBA_MONITORING' AND category_class=2)

BEGIN

EXEC msdb.dbo.sp_add_category

    @class=N'ALERT',

    @type=N'NONE',

    @name=N'DBA_MONITORING' ;

END

GO

IF  EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'SQL Server Severity Event 19')

    EXEC msdb.dbo.sp_delete_alert @name=N'SQL Server Severity Event 19'

GO

USE [msdb]

GO

EXEC msdb.dbo.sp_add_alert @name=N'SQL Server Severity Event 19',

        @message_id=0,

        @severity=19,

        @enabled=1,

        @delay_between_responses=60,

        @include_event_description_in=1,

        @category_name=N'DBA_MONITORING',

        @job_id=N'00000000-0000-0000-0000-000000000000'

GO

EXEC msdb.dbo.sp_add_notification @alert_name=N'SQL Server Severity Event 19', @operator_name=N'YourSQLDba_Operator', @notification_method = 1

GO

USE [msdb]

GO

IF NOT EXISTS(SELECT 1 FROM msdb.dbo.syscategories WHERE NAME='DBA_MONITORING' AND category_class=2)

BEGIN

EXEC msdb.dbo.sp_add_category

    @class=N'ALERT',

    @type=N'NONE',

    @name=N'DBA_MONITORING' ;

END

GO

IF  EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'SQL Server Severity Event 20')

        EXEC msdb.dbo.sp_delete_alert @name=N'SQL Server Severity Event 20'

GO

USE [msdb]

GO

EXEC msdb.dbo.sp_add_alert @name=N'SQL Server Severity Event 20',

        @message_id=0,

        @severity=20,

        @enabled=1,

        @delay_between_responses=60,

        @include_event_description_in=1,

        @category_name=N'DBA_MONITORING',

        @job_id=N'00000000-0000-0000-0000-000000000000'

GO

EXEC msdb.dbo.sp_add_notification @alert_name=N'SQL Server Severity Event 20', @operator_name=N'YourSQLDba_Operator', @notification_method = 1

GO

USE [msdb]

GO

IF NOT EXISTS(SELECT 1 FROM msdb.dbo.syscategories WHERE NAME='DBA_MONITORING' AND category_class=2)

BEGIN

EXEC msdb.dbo.sp_add_category

    @class=N'ALERT',

    @type=N'NONE',

    @name=N'DBA_MONITORING' ;

END

GO

IF  EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'SQL Server Severity Event 21')

    EXEC msdb.dbo.sp_delete_alert @name=N'SQL Server Severity Event 21'

GO

USE [msdb]

GO

EXEC msdb.dbo.sp_add_alert @name=N'SQL Server Severity Event 21',

        @message_id=0,

        @severity=21,

        @enabled=1,

        @delay_between_responses=60,

        @include_event_description_in=1,

        @category_name=N'DBA_MONITORING',

        @job_id=N'00000000-0000-0000-0000-000000000000'

GO

EXEC msdb.dbo.sp_add_notification @alert_name=N'SQL Server Severity Event 21', @operator_name=N'YourSQLDba_Operator', @notification_method = 1

GO

USE [msdb]

GO

IF NOT EXISTS(SELECT 1 FROM msdb.dbo.syscategories WHERE NAME='DBA_MONITORING' AND category_class=2)

BEGIN

EXEC msdb.dbo.sp_add_category

    @class=N'ALERT',

    @type=N'NONE',

    @name=N'DBA_MONITORING' ;

END

GO

IF  EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'SQL Server Severity Event 22')

        EXEC msdb.dbo.sp_delete_alert @name=N'SQL Server Severity Event 22'

GO

USE [msdb]

GO

EXEC msdb.dbo.sp_add_alert @name=N'SQL Server Severity Event 22',

        @message_id=0,

        @severity=22,

        @enabled=1,

        @delay_between_responses=60,

        @include_event_description_in=1,

        @category_name=N'DBA_MONITORING',

        @job_id=N'00000000-0000-0000-0000-000000000000'

GO

EXEC msdb.dbo.sp_add_notification @alert_name=N'SQL Server Severity Event 22', @operator_name=N'YourSQLDba_Operator', @notification_method = 1

GO

USE [msdb]

GO

IF NOT EXISTS(SELECT 1 FROM msdb.dbo.syscategories WHERE NAME='DBA_MONITORING' AND category_class=2)

BEGIN

EXEC msdb.dbo.sp_add_category

    @class=N'ALERT',

    @type=N'NONE',

    @name=N'DBA_MONITORING' ;

END

GO

IF  EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'SQL Server Severity Event 23')

        EXEC msdb.dbo.sp_delete_alert @name=N'SQL Server Severity Event 23'

GO

USE [msdb]

GO

EXEC msdb.dbo.sp_add_alert @name=N'SQL Server Severity Event 23',

        @message_id=0,

        @severity=23,

        @enabled=1,

        @delay_between_responses=60,

        @include_event_description_in=1,

        @category_name=N'DBA_MONITORING',

        @job_id=N'00000000-0000-0000-0000-000000000000'

GO

EXEC msdb.dbo.sp_add_notification @alert_name=N'SQL Server Severity Event 23', @operator_name=N'YourSQLDba_Operator', @notification_method = 1

GO

USE [msdb]

GO

IF NOT EXISTS(SELECT 1 FROM msdb.dbo.syscategories WHERE NAME='DBA_MONITORING' AND category_class=2)

BEGIN

EXEC msdb.dbo.sp_add_category

    @class=N'ALERT',

    @type=N'NONE',

    @name=N'DBA_MONITORING' ;

END

GO

IF  EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'SQL Server Severity Event 23')

        EXEC msdb.dbo.sp_delete_alert @name=N'SQL Server Severity Event 23'

GO

USE [msdb]

GO

EXEC msdb.dbo.sp_add_alert @name=N'SQL Server Severity Event 23',

        @message_id=0,

        @severity=23,

        @enabled=1,

        @delay_between_responses=60,

        @include_event_description_in=1,

        @category_name=N'DBA_MONITORING',

        @job_id=N'00000000-0000-0000-0000-000000000000'

GO

EXEC msdb.dbo.sp_add_notification @alert_name=N'SQL Server Severity Event 23', @operator_name=N'YourSQLDba_Operator', @notification_method = 1

GO

USE [msdb]

GO

IF NOT EXISTS(SELECT 1 FROM msdb.dbo.syscategories WHERE NAME='DBA_MONITORING' AND category_class=2)

BEGIN

EXEC msdb.dbo.sp_add_category

    @class=N'ALERT',

    @type=N'NONE',

    @name=N'DBA_MONITORING' ;

END

GO

IF  EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'SQL Server Severity Event 24')

        EXEC msdb.dbo.sp_delete_alert @name=N'SQL Server Severity Event 24'

GO

EXEC msdb.dbo.sp_add_alert @name=N'SQL Server Severity Event 24',

        @message_id=0,

        @severity=24,

        @enabled=1,

        @delay_between_responses=60,

        @include_event_description_in=1,

        @category_name=N'DBA_MONITORING',

        @job_id=N'00000000-0000-0000-0000-000000000000'

GO

EXEC msdb.dbo.sp_add_notification @alert_name=N'SQL Server Severity Event 24', @operator_name=N'YourSQLDba_Operator', @notification_method = 1

GO

USE [msdb]

GO

IF NOT EXISTS(SELECT 1 FROM msdb.dbo.syscategories WHERE NAME='DBA_MONITORING' AND category_class=2)

BEGIN

EXEC msdb.dbo.sp_add_category

    @class=N'ALERT',

    @type=N'NONE',

    @name=N'DBA_MONITORING' ;

END

GO

IF  EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'SQL Server Severity Event 25')

        EXEC msdb.dbo.sp_delete_alert @name=N'SQL Server Severity Event 25'

GO

EXEC msdb.dbo.sp_add_alert @name=N'SQL Server Severity Event 25',

        @message_id=0,

        @severity=25,

        @enabled=1,

        @delay_between_responses=60,

        @include_event_description_in=1,

        @category_name=N'DBA_MONITORING',

        @job_id=N'00000000-0000-0000-0000-000000000000'

GO

EXEC msdb.dbo.sp_add_notification @alert_name=N'SQL Server Severity Event 25', @operator_name=N'YourSQLDba_Operator', @notification_method = 1

GO

执行完上面脚本后，就会建立下面几个告警。当数据库的错误日志出现这些级别的错误信息时，就会收到告警邮件。相当的方便、简单、高效。

MS SQL 监控错误日志的告警信息的更多相关文章

MS SQL 监控数据/日志文件增长
前几天,在所有数据库服务器部署了监控磁盘空间的存储过程和作业后(MS SQL 监控磁盘空间告警),今天突然收到了两封告警邮件,好吧,存储规划是一方面,但是,是不是要分析一下是什么原因造成磁盘空 ...
查看MS SQL SERVER 错误日志
查看目的: 错误日志的查看是确保过程已成功完成(例如,备份和恢复操作,批处理命令,或其他脚本和过程).这可以帮助检测任何当前或潜在的问题,包括自动恢复信息(尤其是如果SQL Server实例已停止并重 ...
2. SQL Server数据库状态监控 - 错误日志
原文:2. SQL Server数据库状态监控 - 错误日志无论是操作系统 (Unix 或者Windows),还是应用程序 (Web 服务,数据库系统等等) ,通常都有自身的日志机制,以便故障时追溯 ...
sql server 错误日志errorlog
一 .概述 SQL Server 将某些系统事件和用户定义事件记录到 SQL Server 错误日志和 Microsoft Windows 应用程序日志中. 这两种日志都会自动给所有记录事件加上时间戳 ...
SQL Server自动化运维系列——监控磁盘剩余空间及SQL Server错误日志（Power Shell）
需求描述在我们的生产环境中,大部分情况下需要有自己的运维体制,包括自己健康状态的检测等.如果发生异常,需要提前预警的,通知形式一般为发邮件告知. 在所有的自检流程中最基础的一个就是磁盘剩余空间检测. ...
SQL Server自动化运维系列 - 监控磁盘剩余空间及SQL Server错误日志（Power Shell）
需求描述在我们的生产环境中,大部分情况下需要有自己的运维体制,包括自己健康状态的检测等.如果发生异常,需要提前预警的,通知形式一般为发邮件告知. 在所有的自检流程中最基础的一个就是磁盘剩余空间检测. ...
SQL Server 自动化运维系列 - 监控磁盘剩余空间及SQL Server错误日志（Power Shell）
需求描述在我们的生产环境中,大部分情况下需要有自己的运维体制,包括自己健康状态的检测等.如果发生异常,需要提前预警的,通知形式一般为发邮件告知. 在所有的自检流程中最基础的一个就是磁盘剩余空间检测. ...
SQL Server 错误日志过滤（ERRORLOG）
一.背景有一天我发现SQL Server服务器的错误日志中包括非常多关于sa用户的登陆错误信息:“Login failed for user 'sa'. 原因: 评估密码时出错.[客户端: XX.X ...
SQL Server代理(5/12)：理解SQL代理错误日志
SQL Server代理是所有实时数据库的核心.代理有很多不明显的用法,因此系统的知识,对于开发人员还是DBA都是有用的.这系列文章会通俗介绍它的很多用法. 如我们在这个系列的前几篇文章所见,SQL ...

随机推荐

GitHub上那些值得一试的JAVA开源库--转
原文地址:http://www.jianshu.com/p/ad40e6dd3789 作为一名程序员,你几乎每天都会使用到GitHub上的那些著名Java第三方库,比如Apache Commons,S ...
C语言第六章多重循环练习
一.循环输入 #include "stdio.h" void main() { char c; do { printf("我告诉你1+1=2\n"); prin ...
learn shell
the basic shell skills. Bourne shell sh ksh Bash psh zsh C shell csh tcsh [root@bogon temp]# cat ...
Go语言异常处理defer\panic\recover
Go语言追求简洁优雅,所以,Go语言不支持传统的 try…catch…finally 这种异常,因为Go语言的设计者们认为,将异常与控制结构混在一起会很容易使得代码变得混乱.因为开发者很容易滥用异常, ...
几款主流PHP框架的优缺点评比
PHP是一种在国内外都比较流行的开源服务器端脚本开发语言.能够适应大中小型项目的开发需求.我们将在这篇文章中向大家介绍几款主流PHP框架及其相关优缺点评比,作为一个参考分享给朋友们. 主要参考的PHP ...
Moon.Orm常见问题问答FAQ
有问题在评论,我看到邮件会尽快回复 1.重点了解Db里面的方法.这是核心. 2.关于查询语句MQL:http://www.cnblogs.com/humble/p/3380065.html 3.关于如 ...
【MVVM Light】新手初识MVVM，你一看就会
一.前言作为一个初入软件业的新手,各种设计模式与框架对我是眼花缭乱的.所以当我接触到这些新知识的时候就希望自己能总结几个步骤,以便更好更方便的在日常工作中进行使用. MVVM顾名思义就是Model- ...
Entity FrameWork 6帮助类
public class BaseDAL { string strConn = ""; public BaseDAL(string connString) { strConn = ...
C#创建目录，文件名过滤特殊字符串，非法字符
string invalid = new string(Path.GetInvalidFileNameChars()) + new string(Path.GetInvalidPathChars()) ...
UVALive 6911---Double Swords(贪心+树状数组（或集合）)
题目链接 https://icpcarchive.ecs.baylor.edu/index.php?option=com_onlinejudge&Itemid=8&page=show_ ...

MS SQL 监控错误日志的告警信息

MS SQL 监控错误日志的告警信息的更多相关文章

随机推荐

热门专题