Integrating with Moogsoft
Moogsoft AIOps is the pioneering AI platform for IT operations, powered by purpose-built machine learning algorithms. Moogsoft helps to improve the detection and remediation of incidents, ensuring continuous service delivery for business.
eG Enterprise integrates with Moogsoft, so that problem events detected by eG can be automatically sent to Moogsoft. Moogsoft then employs machine-learning and AI to analyze, correlate, deduplicate, and virtually share event information with all those responsible for resolving them, so as to slash event MTTR.
To integrate eG Enterprise with Moogsoft, do the following:
- Login to the eG administrative interface.
Select the Manager option from the Settings tile.
Figure 7 will then appear. From the manager settings tree in the left panel of Figure 7, select the ITSM/Collaboration Integration node. The third-party ITSM/Collaboration tools that eG Enterprise can integrate with will be listed in the right panel.
- To enable integration with Moogsoft, first slide the Moogsoft slider in Figure 8 to the right.
Then, specify the following in Figure 8:
- Webhook URL: eG Enterprise uses webhook integration to route eG alerts to Moogsoft. This integration allows the eG manager to POST JSON payloads containing event information to the webhook URL of Moogsoft AIOps. To enable this communication, first specify the webhook URL of Moogsoft AIOps here.
- User and Password: Here, specify the credentials of a valid, basic authentication user, with rights to hit the configured webhook URL and post event details.
Custom payload: Use custom payload to customize the alert information you send to Moogsoft, so that it includes additional static information.
Typically, the details of an eG alert are sent as a JSON file to the configured REST URL. Every piece of information contained within an eG alert - eg., priority, component name, component type etc. - is represented in the JSON file as a $key:$value pair, where 'key' denotes the alert field, and 'value' denotes the actual value of that field at run time. The 'key' is configured based on what the Moogsoft LAM (Link Access Module) supports. For instance, if the LAM represents alarm priorities using the key 'prior', then the same key will be used in the JSON file for denoting alarm priorities. Accordingly, the entry for alarm priority in the JSON file will be $prior:$value. The $value will be Critical, Major, Minor, or Normal, depending upon the actual priority of the alarm being sent.
If you want eG incidents routed to Moogsoft to include additional information, then you can define a Custom Payload for that information as a $key:$value pair. For example, say, you want incidents to indicate the FQDN of the eG manager that generated the incidents. Say that the FQDN of your eG manager is egmanager.innovations.com. To include this information in alerts sent to Moogsoft, do the following:
- First, check whether the Moogsoft LAM supports a 'key' that can be used for capturing the 'source' of alerts/incidents. If no such key exists, then you cannot proceed with the Custom Payload configuration. On the other hand, if such a key is available, then proceed to replace the $key in your Custom Payload specification, with that key value. For the purpose of our example, let us assume that the supports the key named 'source'. In this case therefore, substitute '$key' with 'source'.
- Then, proceed to explicitly specify the FQDN of your eG manager in the place of $value. This is because, you can use the Custom Payload configuration to add only 'static' information - i.e., information that you explicitly configure, and hence will never change. In the case of our example therefore, the $value will be egmanager.innovations.com.
- The complete Custom Payload specification will now be: source:egmanager.innovations.com
- Finally, click the Update button in Figure 8 to save the changes.