Send events to Lumi
In the observability landscape, events are the building blocks that help you understand the state of your system at any given moment. Sending events is an integral step in the event lifecycle, after which you can parse and transform your data and explore it with various queries.
Imply Lumi is an observability warehouse that can integrate with your existing tooling and workflow. Whether you use Lumi as a standalone product or alongside your current setup, consider the following aspects when you send events to Lumi:
- Forwarding agent and communication protocol that fits your infrastructure
- Types of events and data structures you have
- Any transformations or filtering needed for incoming events
Ingestion integrations
You can send events to Lumi through various ingestion integrations. The integration you select depends on your application, performance, and security requirements.
Ingestion protocol strategy
The specific integration you use to send events to Lumi depends on your use case and event forwarding infrastructure. This section presents high-level guidance on which protocol may be suitable for your observability application.
- To get started quickly, upload a CSV or JSON file to Lumi.
- To send events using HTTP requests, such as through the OpenTelemetry Collector:
- For data in the OpenTelemetry Protocol (OTLP): use the OTLP HTTP integration.
- For structured JSON data: use HTTP event collector (HEC).
- If you send events to Splunk® using universal forwarders, configure Splunk-to-Splunk to send events.
- If you send events to Splunk® using heavy forwarders, you can use the following integrations to send events:
- Splunk ingest action to route to S3 (recommended)
- Splunk-to-Splunk
- To ingest events from objects in an Amazon S3 bucket, use the S3 pull integration.
To learn about Lumi as it relates to the Splunk ecosystem, see Lumi concepts for Splunk users.
The following diagram summarizes these strategies:

Event transformation
To transform events in Lumi, you create a pipeline and define processors as components in the pipeline. You can enrich incoming events with relevant metadata, extract key features from structured formats, or perform other processing tasks. For more information, see Transform events.
Learn more
For tutorials on the send methods, see the following topics:
- How to send events with the OTel collector
- How to send events with an S3 ingest action
- How to send events with S2S
See the Quickstart and File upload reference for details on uploading files to Lumi.
📄️ 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 routing
Tutorial to send events to Imply Lumi using a Splunk® S3 ingest action.
📄️ 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 for Windows event logs
Tutorial on how to send Windows event logs to Imply Lumi using Splunk® S3 routing.