Skip to main content

Data Sources

Data enters the Platform from a Data Source. The first step in collecting data is getting access to the data: this requires "connecting" the data source to the pipeline.

You define how to connect to a data source by its protocol or type. The Platform supports the following data source types:

  1. Plugin Data Source
  2. API Pull
  3. HTTPs Event Collector (HEC)
  4. Prometheus
  5. Kinesis Stream
  6. AWS S3
  7. AWS S3 with SQS
  8. Webhook
  9. Cloud Syslog
  10. Management Queue

Notice that this is not a product list, such as CrowdStrike Falcon or SentinelOne. Connecting to a data source is just a means to move the data from the product. Products often document multiple connection means.

Where is the Add button?​

There are three (3) columns on the Platform page (Platform in the navigation rail), where data collection is configured: Sources, Routers, and Sinks. The Sources column is the definition of the data sources. At the bottom of that column is the Add Source + button.

Platform page showing the pipeline diagram with a column of sources on the left, routers with their pipes in the middle, and sinks on the right, joined by connection lines, with Add Source, Add Router, and Add Sink buttons at the foot of the columns

Each source card shows a type icon, the source name, and a label for the transport that feeds it, for example Plugin Data Source (data pulled by an installed application), Mgmt Queue (an internal management queue), AWS S3 w/ SQS (an S3 bucket read via SQS notifications), or Cloud Syslog. The outline reports the source's state: green while it is actively moving data, gray while it is idle, and red, with an exclamation mark (!) above the card, when it is in error. A green source can also carry a small green throughput graph above the card's upper-right corner; an idle one has none. A colored line runs from the source's output port to the router it feeds.

Clicking Add Source + begins the process.

Configuration​

Add Source + opens the Adding Data Source panel. The first step is to choose the way you want to import that data source, in the Type list; Plugin Data Source is chosen when the panel opens:

The Type list open in the Adding Data Source panel, listing Plugin Data Source, API Pull, HTTPs Event Collector, Prometheus, Kinesis Stream, AWS S3, AWS S3 w/ SQS, Webhook, Cloud Syslog, and Mgmt Queue

Once a type is chosen, the fields needed for that connector appear, on a Basic Info tab and, for most types, an Advanced tab for the source's properties JSON and its FPL receiver. Required fields carry an asterisk (*). Save at the foot creates the source; × closes the panel without saving. Adding a Source lists every type's fields.

Adding Data Source panel with Type set to API Pull, showing Name, Format JSON, Integration, Processor, and Poll Interval (seconds) 300

Naming the Pipe​

Regardless of the type of data source you are configuring, every pipe has a name. This is similar to a file name in an operating system. This is the name that will appear in the Configuration panel. It will also be used when reviewing the platform's usage and metrics charts: the Events tab of the source's panel on the Platform page (v1: Platform → Usage).

When naming the pipe, give it a name that lets users know what type of data is coming from this source, like "Fortinet Firewalls."

Reconfiguring a Data Source​

Click the source's card to open its panel. The Details tab shows its settings. The Active switch under STATUS turns the source off and on, after a confirmation; Disconnect Source From Router, at the panel's foot, takes an inactive source off its router, and Reboot restarts it. Once the source feeds no router, Delete takes the place of Disconnect Source From Router: a source is deleted only after it has been disconnected. See Source Panel.

Not all fields can be edited. In some cases, it is easier to:

  1. Create a new data source connector.
  2. Stop the old data source.
  3. Delete the previous connection.
  4. Connect the new data source to the processor.
  5. Start the new source.
  6. Validate the new source is operating correctly.
  7. Delete the old data source connector.

Demo​

An interactive demo of adding a data source is available here: Adding a Data Source (Storylane)