Solution like SnowFlake for logs / telemetry where compute and storage are separated might be the future.
Solution like SnowFlake for logs / telemetry where compute and storage are separated might be the future.
Decoupling compute and storage is definitely the way to go. We’re using Lambda functions and ECS Fargate containers for compute that scales up and down rapidly, and S3 for storage. Getting ~1TB/sec log scan speeds, which feels fairly good. We keep sparse indices in S3 to narrow down regions of logs to scan. Eg. if you’re searching for an IP address that appears 10 times in a 25TB log set, the indices reduce the search space to around 300MB. Takes a few seconds to complete that query, whereas Athena and CloudWatch take like 20 minutes.
We’re also using Rust to maximize memory efficiency and speed - there are lots of great SIMD optimized string search and regex libraries on crates.io.
We’re early, so there are a lot of SIEM features like detection rules that we are still building. But Splunk/DataDog users might find it useful if costs are a problem and they use mostly log search:
- panther siem (python alerts, thank the lord) and then pandas + databricks + s3 data lakes for deep analysis and IR
- maybe swap in panther SIEM for XDRs, if they get better out of the box