Installation is straight forward however, there are a few prerequisites:
- The individual performing this installation has a small bit of Linux experience.
- Root access is available.
- Internet access is required for installing any missing, but required software packages.
- NMIS must be installed on the same server that opEvents is being installed on. If you do not yet have a working installation of NMIS in your server, please follow the procedure in the NMIS 8 Installation Guide and install NMIS before installing opEvents.
- You will need a license for opEvents. (Evaluation available HERE)
All licenses are added/updated at https://<hostname>/omk/opLicense .
Follow the link below and begin the download.
After opEvents is downloaded, view and follow the Installation guide below.
Basic overview and concepts
1. Understand the different menu options and what they accomplish in opEvents.
2. Descriptions and lists of common Event Log entries to help in understanding what causes each event.
3. Learning Common Node Properties. A number of Opmantek products use a common node configuration infrastructure, which supports standard, product-specific and custom node attributes.
4. opEvents can process information from a variety of sources, some of which can be extended to suit non-standard deployments. Including parsing syslogs, event logs, etc.
Setting priority levels and creating Event Actions and Escalations
1. Understand the different priority levels. opEvents uses its own set of numeric priorities for events, ranging from 0 to 10. This priority value is saved in the
priority event property.
2. Create custom Event Actions and Escalations. opEvents provides the Event Action Policy as a flexible mechanism for reacting to events.
3. Set up custom Policies and Actions.
Every engineer is different as are their networks. Having the ability to customize opEvents to your environments needs is what makes it such a great tool.