Getting Data In

Average over time

bcross64
Explorer

I apologize if this has already been posted, but I think I am not really sure how to word the question. I am ingesting a large amount of data from several Windows computers through perfmon. I am reading processor, memory and disk statistics every 5 seconds. Of course, I will never need this fidelity in a report. Is there a way to ingest the statistics, take an average every minute, save the result and discard the original data?

Tags (2)
1 Solution

dwaddle
SplunkTrust
SplunkTrust

There's summary indexing -- http://docs.splunk.com/Documentation/Splunk/5.0.5/Knowledge/Configuresummaryindexes .. But it really does not address the "discard the original data" part. Summary indexes are "free" (they do not count against your license) and they can be kept on a longer retention than the original indexes they are created from. So you could have your perfmon index with only a 14 day retention (for example) and then have a summary_perfmon index maintained at a longer retention.

View solution in original post

dwaddle
SplunkTrust
SplunkTrust

There's summary indexing -- http://docs.splunk.com/Documentation/Splunk/5.0.5/Knowledge/Configuresummaryindexes .. But it really does not address the "discard the original data" part. Summary indexes are "free" (they do not count against your license) and they can be kept on a longer retention than the original indexes they are created from. So you could have your perfmon index with only a 14 day retention (for example) and then have a summary_perfmon index maintained at a longer retention.

lukejadamec
Super Champion

Summary indexing sound perfect for your needs.
Understand that summary indexes save statistics as data, not the data they were generated from, so spend time to decide exactly what statistics you want to save. For example: CPU - 5 minute average, 5 minute min, 5 minute max, and a time stamp per server. This will boil down 5 minutes worth of CPU logs for all servers into just 5 pieces of data per server, and save it in a separate index, which makes it very fast to search. The catch is, the data in the summary index cannot be rehydrated - a new search on the raw data is necessary.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Developer Spotlight with Denis Gladkikh

From Splunk Engineer to Kubernetes App Builder Denis GladkikhWhat happens when a lifelong developer turns a ...

Governing Enterprise AI, Bringing Cisco Telemetry Home, and More from Splunk Lantern

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...