Ingest telemetry data with source plugins
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.
AbsoluteAmazon Kinesis FirehoseAmazon Kinesis Stream InputAzure Event GridAzure Event HubsBash CommandCloudflare LogPushConfluent CloudDatadog AgentDatagenDummy logs, metrics, and tracesDummy HTTPElasticsearch HTTPFluent BitFluentdForwardGoogle Cloud PubSub InputGoogle Workspace Audit LogsHTTPHTTP API collectorKafkaKubernetes Events Mandiant ASMMicrosoft Intune - Audit eventMock DataOkta System Logs CollectorOpenTelemetryPrometheus Remote WritePrometheus ScrapeS3 Input (One Time)S3 Input (SQS)Signal SciencesSlackSplunk HECSplunk UFSQL DB InputSyslogTCPTelegrafVectra M365 - Incident DetectionVercel 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.