Scanner for Splunk
Run search queries on your high-volume logs in S3 directly from Splunk via custom commands.
Last updated
Run search queries on your high-volume logs in S3 directly from Splunk via custom commands.
Last updated
Scanner provides a Splunk app that allows teams to rapidly search their object storage logs directly from Splunk.
It introduces two custom search commands system-wide in Splunk: scanner and scannertable.
Indexing high-volume log sources in Splunk is often very expensive. Teams can reduce costs dramatically by redirecting these logs to S3 and using Scanner to index them at much lower cost, sometimes 80-90% less than Splunk.
It is still useful to query these high-volume log sources from Splunk, and Scanner allows you to do this at high speed, especially for needle-in-haystack queries. For example, searching a 100TB log data set for a list of IP addresses, emails, or UUIDs takes only 10 seconds in Scanner. Running the same search in a 1PB log data set takes about 100 seconds. This can be 10-100x faster than tools like Athena, especially against raw JSON logs that have not yet been highly optimized with Parquet and partitioning.
You can also execute Scanner queries to populate dashboards in Splunk. It is almost always best to use the scannertable command with dashboard queries since widgets tend to consume data in tabular format.
For example, this query computes aggregated counts of all S3 CloudTrail log events that are not GetObject. We can use it to generate a bar chart in the dashboard.
If you want Splunk to be your single pane of glass where you can analyze both Splunk logs and the logs you have in object storage, Scanner can help you make this happen.
Using Scanner, you can run fast queries against your object storage logs, join them against your Splunk logs, create dashboards from object storage logs, and more.
With your object storage logs easily queryable from Splunk, you can avoid blind spots and keep Splunk costs low.
scanner command returns results as log events
scannertable