Configure your instance to ingest events and metrics using the APEX AIOps Incident Management UI, or by using JSON data and the Incident Management APIs. Read Ingestion methods for an overview of ingestion methods. The tables which follow outline some key differences between various ingestion methods.
Your instance can ingest events and metrics through a number of different mechanisms; some via pull-based and others through push-based ingestion.
Pull-based ingestion types include integrations like Amazon Cloudwatch and Azure and some collector plugins.
Push-based integrations include integrations like CYOI, Events API, Metrics API, and some collector plugins. The push-based integrations provide an API that can be called to push the data.
The following ingestion tables list our supported integrations and information about each integration. The tables include:
The type of ingestion method.
Support for events, metrics or both.
Whether the ingestion method is UI-based or requires command line API actions.
Whether the ingested data is mapped by default, requires mapping, or allows customizable mappings.
Whether you can customize the event deduplication key when you configure the ingestion. (You can modify deduplication keys after ingestion using the Workflow Engine.)
Note
Some of these ingestion methods require a valid API key to work. To create a new API key to use with your ingestion method, read Create an API key.
The app-based ingestion methods are listed by product name and provide a comparative summary about each integration.
Product name | Ingestion method | Events & Metrics | UI-based | Mapping | Deduplication key |
|---|---|---|---|---|---|
Cloud-to-Cloud | Both | Yes | Yes | No | |
| Events | Instructions in the UI | Optional | Optional | |
AppDynamics (pre-configured) |
| Events | Yes, with some UI-based instructions | Optional | Optional |
| Events | Instructions in the UI | Optional | Optional | |
Cloud-to-Cloud | Both | Yes | Mapping specified | No | |
| Both | Only CYOI portion | Yes | No | |
| Events | Yes | Mapping varies | Key provided | |
Google Cloud Operations (formerly Stackdriver) |
| Events | Instructions in the UI | Mapping varies | Yes |
Microsoft SCOM (Service Center Operations Manager) |
| Events | Instructions in the UI | Mapping varies | No |
| Events | Instructions in the UI | Mapping varies | No | |
New Relic (pre-configured) |
| Events | Automatic or default mapping | Key provided | |
| Events | Yes | Mapping varies |
| |
| Events | Yes | Optional | Optional | |
| Metrics | Instructions in the UI | No | No | |
| Events | Instructions in the UI | Mapping specified | Yes | |
| Events | Instructions in the UI | Mapping varies | Yes | |
| Metrics | Instructions in the UI | Mapping varies | No | |
| Events | Yes | Mapping varies |
|
Incident Management features collectors that you can install on Linux, Mac, and Windows systems. You can use these collector agents to gather system information and when used in combination with an enabled plugin, they also can gather events, metrics, or both from supported apps. For all collectors, the System plugin is enabled by default.
Product name | Ingestion method | Events & Metrics | UI-based | Mapping | Deduplication key |
|---|---|---|---|---|---|
(local configuration) | Collector agent | Both | Both UI and command line installation. Let's you create and use a JSON-based local configuration file. | Default mapping provided | Default provided |
Linux-based OS (CentOS, Redhat, Ubuntu) | Collector agent | Both | Partially. Requires a cut and paste of a few lines from the UI to a terminal | Default mapping provided | Default provided |
(M1 architecture not currently supported) | Collector agent | Both | Partially. Requires a cut and paste of a few lines from the UI to a terminal | Default mapping provided | Default provided |
Collector agent | Both | UI and installation wizard. Installation can also be done at the command line. | Default mapping provided | Default provided |
Incident Management supports a number of plugins that work in combination with a collector agent to deliver data to Incident Management.
Product name | Ingestion method | Events & Metrics | UI-based | Mapping | Deduplication key |
|---|---|---|---|---|---|
| Both | Yes | Default mapping provided | Default deduplication key provided | |
Collector Plugin | Metrics | Yes | Default mapping provided | Default deduplication key provided | |
| Both | Yes | Default mapping provided | Default deduplication key provided | |
Collector Plugin | Metrics | Yes | Default mapping provided | Default deduplication key provided | |
| Events | Yes | Default mapping provided | Default deduplication key provided | |
| Metrics | Yes | Default mapping provided | Default deduplication key provided | |
| Events | Yes | Default mapping provided | Default deduplication key provided | |
| Metrics | Yes | Default mapping provided | Default deduplication key provided |
Incident Management provides a set of APIs that enable you to perform data ingestion programmatically.
API name | Events & Metrics | Mapping | Methods | Deduplication key |
|---|---|---|---|---|
Either | User specified mapping | GET, PUT, POST | Can be set in the UI | |
Events | Expects data inIncident Management format | POST via script (REST integration via Webhook) | Can be set via terminal Can be set as a field in the JSON payload | |
Metrics | Expects data in format | (POST via script REST integration via Webhook) | Can be set via terminal |