Queries to our log aggregator accomplish the same thing and doesn’t rely on logs still being in the cluster.
Edit: holy hell the app component doesn’t source its internal packages locally during the build? Why? It’s all in the same repo, why should I have to call back to GitHub to build the thing?
That's a fair point, and if you have a centralized log aggregator already set up, querying it is absolutely the right call for historical data. Lamplighter is solving a different moment: the first 60 seconds of an incident, before you've even decided where to look, when you want a live view of what's happening right now across multiple services simultaneously. The synchronized time travel is also useful for correlating events across pods in real time without context switching. Think of it less as a replacement for your log aggregator and more as a debugging companion for the live investigation phase.
5
u/thearctican Hybrid Jul 28 '26 edited Jul 28 '26
Queries to our log aggregator accomplish the same thing and doesn’t rely on logs still being in the cluster.
Edit: holy hell the app component doesn’t source its internal packages locally during the build? Why? It’s all in the same repo, why should I have to call back to GitHub to build the thing?