Date: Fri, 29 Mar 2024 12:41:47 +0000 (UTC) Message-ID: <245977547.70005.1711716107060@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_70004_1053663830.1711716107059" ------=_Part_70004_1053663830.1711716107059 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
IDERA SQL Compliance Manager can generate a Status Alert when it= receives a status update from the Collection Server or SQL Compliance Mana= ger Agent that is unsafe and could disrupt your ability to audit your SQL S= erver instances. Alert rules define what type of status is considered unsaf= e and how SQL Compliance Manager should respond. You can configure SQL Comp= liance Manager to write a custom alert message to the application event log= and send an alert email notification to your corporate and personal SMTP a= ccounts when the alert is triggered. For more information, see Use Status Alerts to = ensure compliance.
There are two categories of Status Alerts:
In general, when the Collection Server or SQL Compliance Manager Agent c= ommunicates at their heartbeat intervals, each service confirms its health = and compares its status information against the alert rules you have define= d. An alert message is generated when the status is deemed unsafe. By defau= lt, each heartbeat occurs in five-minute intervals.
Depending on the amount of alert activity your environment generates, yo=
u may want to groom alert messages on a routine basis. For more information=
, see Groom alerts.