Skip to main content
Chronosphere Telemetry Pipeline uses source plugins to ingest telemetry data into pipelines, either by receiving it (push) or collecting it (pull). You can add and configure source plugins to connect your pipelines to a variety of telemetry sources. Different source plugins support different data types, including logs, metrics, and traces.

Absolute

Amazon Kinesis Firehose

Amazon Kinesis Stream Input

Azure Event Grid

Azure Event Hubs

Bash Command

Cloudflare LogPush

Confluent Cloud

Datadog Agent

Datagen

Dummy logs, metrics, and traces

Dummy HTTP

Elasticsearch HTTP

Fluent Bit

Fluentd

Forward

Google Cloud PubSub Input

Google Workspace Audit Logs

HTTP

HTTP API collector

Kafka

Kubernetes Events

Mandiant ASM

Microsoft Intune - Audit event

Mock Data

Okta System Logs Collector

OpenTelemetry

Prometheus Remote Write

Prometheus Scrape

S3 Input (One Time)

S3 Input (SQS)

Signal Sciences

Slack

Splunk HEC

Splunk UF

SQL DB Input

Syslog

TCP

Telegraf

Vectra M365 - Incident Detection

Vercel Logs

​
Push-based and pull-based source plugins

Source plugins are either push-based or pull-based.
  • Push-based source plugins passively listen for data emitted from a specified source.
  • Pull-based source plugins actively fetch data from a specified source.
However, source plugins that output test data, like Datagen, are classified as pull-based plugins even though they don’t communicate with external sources.