Brittany Kaler At .conf25, Splunk set the tone: digital resilience in the AI era.
From AI-powered SOCs to agentic observability, the message was clear, resilience is about visibility, speed, and smarter response.
But resilience truly starts with the data. If dashboards or AI can’t reach it—because it’s archived, siloed, or too expensive to keep hot, resilience falls apart.
That’s the gap Imply Lumi, the industry’s first Observability Warehouse, was built to fill.
And in Boston, we announced Imply Lumi to the Splunk world for the very first time!
Walking the floor and talking with observability admins in attendance, we heard their challenges loud and clear:
If this sounds familiar, it should. Business Intelligence went through the same shift: data outgrew monolithic stacks, and the real innovation came from decoupling storage from compute.
Observability is now at that same breaking point.
We came to Boston as part of the Splunk Partnerverse, showing how Imply Lumi — the industry’s first Observability Warehouse — makes Splunk even more powerful while reducing costs.
Splunk remains the command center: the dashboards, alerts, and workflows your teams already know and trust. But underneath, Imply Lumi becomes the engine — a high-performance, cost-efficient warehouse that keeps more logs, metrics, and traces hot and instantly searchable.
The result? Splunk admins gain the freedom to do more:
This vision builds on what Splunk has already signaled with Federated Search: the ability to analyze data without moving it.
Imply Lumi takes that vision further — decoupling source, storage/compute, and interactive layers — and brings the performance, scale, and economics of a modern warehouse to every Splunk deployment.
With Splunk and Imply Lumi, enterprises can store more, search faster, and stop choosing between cost and visibility.
Admins who joined us at Splunk .conf25 didn’t just hear about Imply Lumi — they experienced it in action, working seamlessly alongside Splunk.
In our breakout sessions — “Say Yes to More Data: Extend Your Splunk Investment” and “Unlock More Use Cases Without Breaking the Bank” — we showed how Imply Lumi helps Splunk admins keep more data searchable, extend Splunk into new workloads, and support more teams without breaking budgets.
At the booth, those ideas came to life. Visitors watched their Splunk dashboards load in seconds, even across months of historical data. They saw storage footprints shrink by more than 50% without losing fidelity. They discovered that AI/ML workflows — from ChatGPT to Claude to LangChain — could query Lumi directly. And they saw Splunk side by side with Grafana, Tableau, and other tools, all powered by the same Imply Lumi data layer.
The outcome was clear: admins walked away with more freedom to say yes — yes to more data, yes to more use cases, and yes to delivering a bigger impact across their organizations.
“I’ve been told this is the most exciting product in the room, so I stopped by.” — Splunk .conf attendee
Our first Splunk .conf wasn’t just a debut — it was a new chapter for Splunk customers: more resilience, more reach, and more room to grow with Imply Lumi.
Book an Imply Lumi demo
Read the Imply Lumi announcement
And this is just the beginning. Next year, when .conf26 lands in Denver, we’ll be back with bigger stories, faster demos, and more ways for Splunk admins to unlock the full potential of their data.
With Imply Lumi, Splunk admins have the freedom to do more.
Why You Shouldn’t Have to Delete Your VPC Flow Logs
When a security incident happens, investigators almost always start with the same questions: Which systems communicated? Where did the traffic originate? What changed before the incident? Was data exfiltrated?...
Learn MoreSplunk Smartstore vs Lumi Loglake: Two Very Different Ways to Search Logs in Object Storage
One copies data back before it can be searched. The other queries it where it lives. Lumi Loglake lets Splunk teams query logs directly in object storage, including AWS S3, Delta Lake, Apache Iceberg, using...
Learn MoreSupercharging Schema-On-Read: Logs in Object Storage Don’t Need a Data Catalog
Machine data architectures are rapidly changing. As telemetry volumes continue to grow and as costs rise, organizations are increasingly moving logs and other machine data into object stores such as AWS S3....
Learn More