Ingestion services

Watch a product demo: Data Ingestion Methods in Moogsoft ►

Integrations make it possible for Moogsoft to ingest data from a variety of monitoring tools. This process centralizes your data and lets you use the features available in Moogsoft to add value to the data you're already collecting. Ingested data may take the form of events or metrics, depending on the integration.

After you've set up an integration and your monitoring data is flowing into Moogsoft, you can:

  • View metrics in a graphical interface with duplicated, repeated, and obsolete events removed from the data stream, so you can more easily identify important or unique events.

  • Detect anomalies using configurable metrics parameters.

  • Enrich metrics with workflows to make them more meaningful. For example, you can indicate applications which cause certain events or group together related events.

  • Cluster related alerts into incidents which you can then assign to other users and set statuses.

  • Use the correlation engine algorithms to build custom rules that cluster certain related alerts into incidents.

In most cases, integrations take just a few minutes to configure.

Moogsoft uses three methods to create inbound integrations:

  • Collector

    The Moogsoft Collector lets you ingest data and chart multiple metrics using a variety of built-in plugins. The data displayed is system dependent, depending on the operating system, configured features, and other parameters.Collectors

  • Supported integrations

    These integrations require minimal user input and are quick to configure using forms available in Moogsoft. The features for each supported integration vary. Some supported integrations include AWS CloudWatch and Datadog.

  • API Webhooks

    You can use the Create Your Own Integration (CYOI) feature to set up a custom API endpoint in Moogsoft to listen for communications from a webhook in your source monitoring tool. Your integration and data are clearly identified by a name of your choosing within Moogsoft. Custom mapping your payload fields allows translation of source data to Moogsoft.

    Step-by-step instructions for configuring integrations with several popular monitoring tools are available. Many others are possible using a webhook in your monitoring tool, custom mappings, and your custom CYOI endpoint.

In addition to inbound integrations, Moogsoft also includes outbound integrations. Refer to the related topics for more information.

Comparison of ingestion methods

The following table outlines some key differences between various ingestion methods.

Ingestion Method

What it is

UI-based

Mapping schema

Can you specify the deduplication_key combination?

Time series data

Source system

Detect anomaly at the edge

Only collects predetermined metrics

CYOI

API-based integration tools

Yes

Flexible, handled in Moogsoft

Yes

Yes

Anything

No

No

Event API

API-based integration tools

Yes, but optionally via terminal also

Specified, handled in the source system

Yes

No

Anything

N/A

N/A

Metric API

API-based integration tools

Yes, but optionally via terminal also

Specified, handled in the source system

Advanced only

Yes

Anything

No

No

Collector

Agent

Yes

Specified

Advanced only

Yes

EC2, Docker, CentOS, MongoDB, Redhat, Reddis, Ubuntu

Yes

Yes

Cloud to Cloud

Product-specific integration tools

No

Specified

Advanced only

Yes

Azure, Datadog, Cloudwatch

No

Yes

Documented push integrations

Documented webhook integration with a specific product that uses either the events/metrics or CYOI APIs

No

Varies

Advanced only

Yes

Appdynamics, Dynatrace, Nagios, New Relic, Pingdom, Stackdriver, Sumo Logic, SCOM, Zabbix

No

No

Published 2021-11-18T20:45:37-05:00