Lumi integrations
You can integrate Imply Lumi with your existing observability tools and workflows in many ways. This topic provides a quick reference of available integrations by type to help you find the most relevant documents for your observability environment.
Ingestion integrations
Ingestion integrations enable you to add data to Lumi, either by sending data or consuming data from an external source. For more information about choosing an ingestion integration see Ingestion integrations.
| Source | Description | Docs |
|---|---|---|
| File upload | Upload a CSV file or NDJSON in the Lumi UI. Recommended for evaluation purposes. | File upload reference |
| HTTP sources | Use the HTTP client of your choice to send JSON-formatted events to the Lumi HEC endpoint or OTLP endpoint. | Send events with HEC Send events with OTLP |
| OpenTelemetry collector | Configure the OTel collector to send events to the Lumi HEC endpoint or OTLP endpoint. | Send events with HEC Send events with OTLP |
| Splunk® heavy forwarder | Configure the heavy forwarder to send events to Lumi using S2S or an ingest action. | Send events with S2S Send events with S3 routing |
| Splunk universal forwarder | Configure the universal forwarder to send events to Lumi using S2S. | Send events with S2S |
Application integrations
You can set up application integrations to access events in Lumi using third party tools.
| Tool | Description | Docs |
|---|---|---|
| Claude Code | Query your Lumi event data using the Claude CLI. | Coming soon |
| Claude Desktop | Query your Lumi event data using a Claude Desktop MCP extension for Lumi. | Coming soon |
| Grafana | Query Lumi events in Grafana. | Search events with Grafana |
| Splunk | Set up Lumi as a federated search provider for Splunk. | Set up Splunk federated search |
| VS Code / GitHub Copilot | Connect to the Lumi MCP server to query events with Copilot. | TBD |