Integrations and LAMs
Integrations are the broad term for processes which interact with external third party (vendor) systems, both for event ingestion and outbound requests. Depending on which type of integration you install, the processing workflow varies.
You configure integrations from the UI. Doing so allows you to configure multiple instances of an integration.
There are five types of integrations: Monitoring, Notification & Collaboration, Reporting & Dashboards, Ticketing, and Workflow Engine.
For monitoring integrations, you can alternatively configure LAMs instead of the integration. Like integrations, LAMs are groups of processes which ingest event data for a third party vendor. However, a LAM is separate from an integration and does not involve any UI configuration.
The following key differences also apply to LAMs:
LAMs allow you to configure more complex properties for data ingestion which are unavailable in the integrations UI for a data source. For example, to enable high availability.
You configure and run LAMs from the command line interface.
While some integrations allow you to configure multiple instances of that integration, you can only configure one LAM for each data source.
Note
For monitoring data sources, you configure either the integration or the LAM. You cannot configure both.
The following sections describe each integration type:
Monitoring
The most common type, these LAMs and integrations either push event data (via a webhook) from their native application to Moogsoft Onprem, or periodically polls the integrated application for that new data.
Example integration: Sensu
Notification & Collaboration
Integrations of this type connect to Moogsoft Onprem, to receive notifications about new alerts and events on their collaboration platform.
Example integration: Slack
Reporting & Dashboards
Integrations of this type provide deep insights into the state of your operations.
Example integration: Grafana
Ticketing
Integrations of this type synchronize with Moogsoft Onprem to receive new alert and event data, from which you can create corresponding tickets in the integrated application. They do not have corresponding LAMs to configure.
Example integration: JIRA Service Desk
Workflow Engine
Integrations of this type connect a data source to Moogsoft Onprem, which prepares incoming data for further processing in the Workflow Engine. They do not have corresponding LAMs to configure.
Example integration: JDBC Enrichment