Beyond basic event management

The Best Practices discussed in this section provide a good foundation on which to build your event management strategy.

However, there are many ways to expand that strategy. For example, you can perform additional notification by sending e-mail messages and communicating with wireless devices, including pagers, as described in Reference for BMC AMI Ops Automation solutions.

You can also take advantage of the integration between BMC products and other products to show the impact of mainframe outages and slowdowns on critical business services. For example, you can:

Related topic

Send events from BMC AMI Ops Automation to BMC Impact Manager from a Rule or EXEC, as described in Using the BiiZ component of BMC AMI Ops Automation
Send notification requests from BMC AMI Ops Automation to AlarmPoint, which manages various notification methods and problem escalation
Use BMC AMI Ops Automation to send Simple Network Management Protocol (SNMP) traps to other event management systems, such as IBM Tivoli Enterprise Console or Computer Associates Unicenter, as described in Reference for BMC AMI Ops Automation solutions
Publish BMC AMI Ops Automation alerts to General Messages Exchange (GME) connections, as described in Using Rules with BMC AMI Ops Automation
Open trouble tickets with an incident tracking product (such as Helix ITSM), either by publishing BMC AMI Ops Automation alerts to GME connections, or by sending email messages generated by BMC AMI Ops Automation to an incident tracking product that supports receiving email reports of issues. For more information, refer to Using Rules with BMC AMI Ops Automation and Customizing a GME connection for opening tickets.

These methodologies and products can help you evolve your event management strategy even further—to fully align your IT infrastructure with your business services goals.

Beyond basic event management

On this page