Skip to main content
Skip table of contents

Data Ingestion

The Data Ingestion module shows a complete list of all ingested events and incidents by data sources. This module is divided into two tabs:

  • Event Intake

  • Incident Intake

Intake Methods for Data Sources

There are three methods you can use to ingest data into D3 SOAR:

  • Schedule: Schedule a Fetch Event/Incident Command to ingest data

  • Webhook: Use a webhook to push data into the system

  • File: Upload Files to ingest Event data (For details on how to ingest data by file upload, please refer to Investigation Dashboard)

UI Structure

The Data Ingestion module’s UI contains the following components:

Data Ingestion List

This section displays the list of configured Data Ingestion schedules. You can find two different types of Data Ingestion methods here: Schedule and Webhook. At the top of the section, there is a search bar to help you search for the schedule you need.

Data ingestion schedules are sorted by integration by default, but you can also sort by sites. Sorting by sites will nest all integrations and data ingestion schedules under that particular site.

Schedule Log

This section displays the list of logs of past runs of the selected schedule. Here, you can see all past runs of this schedule and filter them by time and status.

Data Ingestion Details

This section shows all the log details of a specific run. The information is categorized into five tabs: Input Data, Output Data, Raw Data, Event List, Incident List (only in Incident Intake), and Error Log.

Data Ingestion Card

A data ingestion card displays the schedule’s Site information and Connection information. There are a few actions you can take on a Schedule:




This action stops this schedule.


Clone this schedule’s configuration.


View the current configuration for this fetched schedule.


Delete this schedule and its associated logs.

Reader Note

You cannot restart a stopped schedule, but you can clone a stopped schedule to run it again.

In addition, the status tag on the right displays the current state of the fetch Schedule:



This indicates that the fetch schedule is currently active and running.

This indicates that the Fetch schedule has been manually stopped.

Reader Note

Creating a new Ingestion Method for an Incident Intake is similar to the Event Intake instructions above. The only difference is that you will need to select the Incident Intake tab instead of the Event Intake.

Configuring Fetch Event Data Ingestion

Below are instructions on how to configure Schedule and Webhook as Intake Methods. Data ingestion by files can be done in the Investigation Dashboard.


To configure a new Fetch Event schedule:

  1. Click on the Data Ingestion tab.

  2. Hover over the desired Data Source or the + icon next to the Search bar.

  3. Click on the + icon.

  1. Select Schedule as the Intake Method.

Reader Note

The availability of intake methods depends on the integration and user configuration. Some integrations have webhook as well.

  1. (Optional) Setup Event Field Mapping

  1. Select a Connection.

  2. Set the Interval. This determines how often the schedule executes.

  3. Select an Event Playbook that you wish to run on this scheduled data ingestion.

  4. (Optional) If the connection is shared with all clients, fill this box in with the JSON path for the client site that the ingested event will appear in.

  5. (Optional) In the case that the event raw data JSON does not contain a site field, users can use a Global List that specifies a series of sites.
    The list should contain an array of sites like below:

         "d3security": "D3 Site",
          "site2": "Client Site 2",
           "site3": "Client Site 3"

Reader Note

If no site that matches can be found or no site is specified, D3 system will create a new site called (Unknown Client Site) to ingest the subsequent events.

  1. Check the box if you want to receive email notifications after a certain number of failed attempts.

  2. Fill in the inputs for the Fetch Event command in Command Details. (Command details may vary depending on the integration)

  3. Click on Save & Run


The new Data Source will be displayed as a card on the left hand side and the schedule will start running.


The Webhook ingestion method allows the Integration to send event or incident data (in JSON format) to be investigated in the D3 vSOC platform. This allows real-time, controlled event or incident data ingestion for SOC teams, and offers greater flexibility.

The following is a general how-to for setting an Event Ingestion webhook.

  1. Click on the Event Intake tab.

  2. Hover over the desired Data Source or the + icon next to the Search bar.

  3. Click on the + icon.

  1. Select Webhook as the Intake Method

  2. (Optional) Setup Event Field Mapping

  1. Select a Site from the dropdown list. Here you have the option to select an individual site or share a key between all client/internal sites. Keys that are shared to internal/client sites can be used to ingest events ingest events into internal/client site.

  2. Click on generate to create a new Authentication Key.

  3. (Optional) Select an Event Playbook from the drop-down. This determines which event playbook will be run upon ingestion.

  4. (Optional) Select a Data Formatter to run a data formatter command on the incoming event after ingestion. Data formatter commands can be configured in Utility Command by checking the “Event/Incident Data Formatter” feature.

  5. Once the key is generated, it will be listed under the site header. For a key shared to all sites, you can then use the dropdown in Request URL to select the site URL for the key post. If you wish to generate a new key, use the Generate button on the top right.

  6. Click on Save & Run.

  1. The new Data Source will be displayed as a card on the left hand side.

  2. Click on the eye icon of the webhook card to view the details, the key post and key can now be copied and used.

Reader Note

A shared to All Internal/Client site webhook key can be used in different sites. Use the same dropdown to select the desired site and copy the new URL.

Reader Note

For incident ingestion, you can select an Event Playbook. The reason is there may be events that are ingested with the incident. Apart from that, incident ingestion through webhook will look and function similarly. We recommend referring to this how-to for setting up an incident intake command as well.

Cloning an Existing Fetch Schedule

  1. Click on the copy button of the schedule you want to clone.

Reader Note

The copy button is only available when a schedule is in the Stopped state.

  1. In the Clone Data Source window, update the input parameters you would like to change, if any. Integration and Intake Method cannot be changed for a clone.

  2. Click on Clone and Start.


The new fetch schedule will be created and appear above the previous fetch schedule card.

View Fetch Schedule Logs

Clicking on any of the Data Sources will display a time log and the imported data on the right-hand side.

You can narrow down this log by date range and/or by status using the filters provided at the top of the list. At a glance, you can view if a run was successful by looking at the icon on the right side of the date and time.




This indicates that the run was successful and Event data has been received.

Done (No Data)

This indicates that the run was successful but no Event data was received.


This indicates that the run was unsuccessful.


This indicates that the run is initiated but there are tasks that haven't run yet.

The data of each run is displayed on the right-most panel, split into tabs:

  1. Input Data: Input parameters of the fetch Event/Incident command

  2. Output Data: Event/Incident data from this scheduled fetch run

  3. Raw Data: Original data pass into the system

  4. Event List: List of Events ingested into the system

  5. Error Log (Only shows if there is error): All error data when the run is unsuccessful

  6. Playbook (Only Playbook Implementation): Runtime Playbook configured for this schedule

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.