Derdack

Targeted Alert Notifications – Anywhere Actions

Derdack
  • Use Cases
    • Overview
    • Enterprise IT Alerting
    • IT Managed Services
    • Mobile Alerting in Manufacuring
    • Critical Operations Alerting in Banking & Financial
    • Field Service Dispatching in Energy & Utilities
    • Use Cases in other Industries
  • Products
    • Overview
    • Enterprise Alert®
      • Overview
      • Alert Notifications
      • On-call Duty Scheduling
      • Collaboration
      • Anywhere Remediation
      • Incident Mgmt. App
      • Integrations
      • Technical Support
      • Derdack FAQ
    • SIGNL4® Cloud
    • References & More
  • How to Buy
    • Overview
    • Pricing and Quotes
    • Find a local Partner
    • Azure Marketplace
  • About Derdack
    • About
    • Careers
    • Partner Program
    • Strategic Partners
    • Contact Derdack
  • News & Blog
  • Request Demo
    • de de
  • News & Blog

    • Home
    • News & Blog
    • Technical
    • How to add additional Event Parameters in Enterprise Alert

    How to add additional Event Parameters in Enterprise Alert

    • October 3, 2015
    • Technical
    How to add additional Event Parameters in Enterprise Alert
    In most cases the parameters that are transferred from SCOM and the other event sources to Enterprise Alert include all the relevant information to be used in the alert policies. However, in some cases additional or custom parameters are required.
    The following example shows how to add additional event parameters for SCOM events, but this applies to other connectors in the same way.
    If you have a look in the XML part of a SCOM event you see all the event parameters coming from SCOM. In some cases there are additional parameters needed in policies, e.g. if you need a certain Alert ID from SCOM.

    The next steps will show you, how to add these parameters:
    1.       Create a backup of your Enterprise Alert database
    2.       Change an option in the database table for the respective Enterprise Alert connector
    3.       Restart the Windows Service of Enterprise Alert
    4.       After this you are able to create a new parameter in the conditions for the alert policy

    Create a backup of your Enterprise Alert database

    In the first step you should create a backup of your Enterprise Alert database to be able to roll back in case of an issues.

    Change an option in the database table for the Enterprise Alert connectors

    To enable a new parameter, that is not part of the default list, you have to set a permission in the database table for the connectors. Therefore you have to sign in to the Enterprise Alert database, choose the table “EventProviders” and change the value in the row “Options” from 16 to 18 for the “MOM Connector” which represents SCOM, as shown in the figure below.

    Restart the Windows Service of Enterprise Alert

    You have to restart the Windows Service of Enterprise Alert, to let the changes take effect. Therefore, you have to open the “Services” window and restart the “Enterprise Alert® 2015 Server” service. After the restart, you should be able to create a new parameter.

    Create a new parameter

    In the next step you can create a new parameter. In the Enterprise Alert Web portal go to “Alerts” à “Alert Policies” and chose an existing alert policy or create a new one and note that the “Event Source” is “System Center Operations Manager”. When setting up the “Conditions” you are now able to choose the item “<<Create New Parameter>>” from the parameter list and enter a new parameter as shown in the figure below. Please note, the parameter is case sensitive.


    Now you are able to use the new parameter in your alert policy under “Conditions” and “Message”.

    Other details

    ·         Note that the parameters are case sensitive. That means “AlertID” is not the same as “alertid”, for example.
    o   In the case that you mistyped the new parameter, you are able to edit it in the table “EventParameters”.
    ·         Generally you can also expand other connectors like HP NNMi, IBM Tivoli, etc., if you change the “Options” value from 16 to 18 in “EventProvider” as shown above.
    Thanks for preparing this article go to Jens Klinger.

    Tagged

    Enterprise AlertSMTPWindows

    Share

    Related Posts

    Empowering Remote Users

    December 9, 2020

    Tips & Tricks: Keeping track of user profile changes

    December 3, 2020

    Secure mobile Authentication with Azure Active Directory

    November 13, 2020

    Enterprise Alert 2019 Update 8.5.1 released

    October 9, 2020

    About

    DERDACK products combine automated alert notification workflows, 24/7 duty scheduling, ad-hoc collaboration and anywhere IT troubleshooting – reducing unexpected IT downtimes at large enterprises and organizations by 60%.

    Most popular

    • Derdack Company Take your ITIL incident management to the next level with Enterprise Alert
    • Mobile alert notifications for HP Service Manager (HPSM)
    • Enterprise Alert® 2015: Flood Protection is so cool!
    • How to forward alerts to Microsoft Teams
    • Oncall Scheduling On-Call Schedule Management with Auto-Rotation
    • checking-mobile Enhancing SCOM alert notifications
    • Even, Alert, Incident, Notification Definition of Event, Alert, Incident and Notification
    • Announcing Enterprise Alert 2019

    Categories

    • Business (34)
    • Customers (13)
    • Energy & Utilities (7)
    • Events (23)
    • Financial & Banking (4)
    • IT Ops (17)
    • Manufacturing (6)
    • News (43)
    • Technical (105)
    • Transport & Logistics (4)

    Tags

    alert alert notification alert notifications Anywhere Resolution Anywhere Response azure Azure customer reference Database derdack enterprise alert Enterprise Alert Enterprise Alert 2016 Enterprise Alert 2019 HPE HPE ITSM incident Incident resolution incident response Industrie 4.0 Integration IT Alerting IT Operations Maintenance microsoft Mobile App monitoring OMS on-call on-call schedule phone PowerShell rapid response release REST API SCADA SCOM scsm security SMTP SolarWinds NPM System Center update User Group voice

    Follow us

    • Twitter
    • Facebook
    • LinkedIn
    • XING
    • YouTube
    • Vimeo
    • Home
    • News & Blog
    • Technical
    • How to add additional Event Parameters in Enterprise Alert

    CONTACT US:
    Intl: +49 331 29878-0

    US: +1 (202) 470-0885
    UK: +44 (20) 88167095

    CONTACT VIA EMAIL:
    info@derdack.com

    OFFICES:
    US & Europe

    NEWSLETTER:
    Sign up here

    CAREER:
    Latest job offers

    EVENTS

    • No Upcoming Events
    • Who we help
    • Products
    • How to Buy
    • About Derdack
    • News & Blog
    • Free Trial
    • Twitter
    • Facebook
    • LinkedIn
    • XING
    • YouTube
    • Vimeo

     © 1999-2021 Derdack – Imprint, Privacy policy

    • Use Cases
      • Overview
      • Enterprise IT Alerting
      • IT Managed Services
      • Mobile Alerting in Manufacuring
      • Critical Operations Alerting in Banking & Financial
      • Field Service Dispatching in Energy & Utilities
      • Use Cases in other Industries
    • Products
      • Overview
      • Enterprise Alert®
        • Overview
        • Alert Notifications
        • On-call Duty Scheduling
        • Collaboration
        • Anywhere Remediation
        • Incident Mgmt. App
        • Integrations
        • Technical Support
        • Derdack FAQ
      • SIGNL4® Cloud
      • References & More
    • How to Buy
      • Overview
      • Pricing and Quotes
      • Find a local Partner
      • Azure Marketplace
    • About Derdack
      • About
      • Careers
      • Partner Program
      • Strategic Partners
      • Contact Derdack
    • News & Blog
    • Request Demo