Learn to send events to Lumi
The first step in getting started with Imply Lumi for your observability workflow is sending data to Lumi.
There are many ways you can send data to Lumi. The approach that's best for you depends on your event logging infrastructure. For example:
- You might have an OpenTelemetry collector that receives telemetry data from Kubernetes.
- You might have logs stored in an Amazon S3 bucket or published to Amazon Data Firehose.
- You might already have a Splunk® universal forwarder set up to monitor system access logs.
In many cases, there will be a protocol to suit your needs, even if it's just sending HTTP requests from your application. To learn about the available integrations for sending events, see Send events to Lumi. There, you can also find strategies to consider to decide which integration fits your use case.
This section provides a series of tutorials for sending events to Lumi. Each tutorial is standalone and focuses on a specific ingestion protocol or data source. You can learn more about each integration from the corresponding guide in Send events. To learn about the tutorial data, see Tutorial data.
If you haven't already, check out the quickstart for how to upload a file and view and query those events.
📄️ How to use OTel
Tutorial to send events to Imply Lumi using OpenTelemetry.
📄️ How to use S2S
Tutorial to send events to Imply Lumi using the Splunk®-to-Splunk protocol.
📄️ How to use S3 pull
Tutorial to send events to Imply Lumi from an Amazon S3 bucket using S3 pull.
📄️ How to use S3 routing
Tutorial to send events to Imply Lumi using a Splunk® S3 ingest action.
📄️ How to use S3 routing for Windows event logs
Tutorial on how to send Windows event logs to Imply Lumi using Splunk® S3 routing.