Alert when an Element is Muted

I am trying to create an alert to trigger if any object is set to Mute. I have the report that looks good but now I want an alert. Any ideas would be helpful.

Parents
  • You can do this via the normal web alerts too. See image below, you may want to delete the unmanaged conditions. This works pretty well for me. The trigger action sends an email with the audit message. THe message includes who and what. Here is the variable string that I use: 

    ${N=SwisEntity;M=AuditEventMessage} on ${N=Generic;M=DateTime;F=DateTime} 

    Trigger condition:

  • - any chance you still have this alert somewhere on a system and can share it to the Alerts Content Exchange?

  • I believe this was intended to be .

    can you provide more details about what is not working. Is it not triggering or not performing your configured actions?

  • You are correct sir - sorry for calling you out there.  That'll teach me to reply via mobile while juggling other threads.  My bad.

  • I created a new alert, but there are still artifacts in the xml output. Custom properties and whatnot. trying to clean them up without breaking the xml. Is there a simple method to do this? 

    Since the question was how to do this, here is a short walk through in lieu of the alert upload.

    Bottom line, create an alert, in the I want to Alert on: Auditing Event

    The scope can be left with default.

    Choosing the trigger condition.. Again Auditing Events, and remember to change the condition to an OR from the default AND.

    Leave the Auditing Event in the trigger condition, for the Field, you will most likely need to choose browse all  fields and select Action Type. Then select Equal To and keep reading for the events. You will need to add five conditions in total.  

    I wish there was a way to sort the events better, they are organized in groups, but not really alphabetically. You can refer to the screenshot in this thread as it is still valid. They will load in the drop down list...

    Look for

    • Node Managed
    • Node Unmanaged
    • Alerts Muted
    • Alerts Unmuted
    • Schedule for muting alerts changed

    The top two node conditions will be next to each other, and the three alert muting conditions will be next to each other also. 

    Frequency for the alert is set to 10 minutes. This still catches things pretty quickly. You can modify if you like. 

    Next, RESET Condition.

    I am currently using the "Reset this alert automatically after ' 1' Minutes. 

    The automatic reset option has been hit or miss in my experience. THis will still catch the events though.

    Trigger actions : setup an email. The swql variable above should work. I will paste below what I tend use with audit events. THe audit event information includes a who what statement, so it is actually sufficient. 

    ${N=SwisEntity;M=AuditEventMessage} on ${N=Generic;M=DateTime;F=DateTime}
    This message was brought to you by the alert named: ${N=Alerting;M=AlertName}

    THere is no reset action and your are basically done. Submit the alert. 

Reply
  • I created a new alert, but there are still artifacts in the xml output. Custom properties and whatnot. trying to clean them up without breaking the xml. Is there a simple method to do this? 

    Since the question was how to do this, here is a short walk through in lieu of the alert upload.

    Bottom line, create an alert, in the I want to Alert on: Auditing Event

    The scope can be left with default.

    Choosing the trigger condition.. Again Auditing Events, and remember to change the condition to an OR from the default AND.

    Leave the Auditing Event in the trigger condition, for the Field, you will most likely need to choose browse all  fields and select Action Type. Then select Equal To and keep reading for the events. You will need to add five conditions in total.  

    I wish there was a way to sort the events better, they are organized in groups, but not really alphabetically. You can refer to the screenshot in this thread as it is still valid. They will load in the drop down list...

    Look for

    • Node Managed
    • Node Unmanaged
    • Alerts Muted
    • Alerts Unmuted
    • Schedule for muting alerts changed

    The top two node conditions will be next to each other, and the three alert muting conditions will be next to each other also. 

    Frequency for the alert is set to 10 minutes. This still catches things pretty quickly. You can modify if you like. 

    Next, RESET Condition.

    I am currently using the "Reset this alert automatically after ' 1' Minutes. 

    The automatic reset option has been hit or miss in my experience. THis will still catch the events though.

    Trigger actions : setup an email. The swql variable above should work. I will paste below what I tend use with audit events. THe audit event information includes a who what statement, so it is actually sufficient. 

    ${N=SwisEntity;M=AuditEventMessage} on ${N=Generic;M=DateTime;F=DateTime}
    This message was brought to you by the alert named: ${N=Alerting;M=AlertName}

    THere is no reset action and your are basically done. Submit the alert. 

Children
No Data