Monitoring Splunk

Is there any way to speed up searches?

tier2ops
Explorer

I have a search that is taking a few days to run.

Here is the search string:

sourcetype="bcoat_proxysg" | stats dc(c_ip) by date

I send the search to the background and can continue to work but I want to know if there is a way to speed up the this search. Thanks.

Other information:

Running Splunk 4.0.11

PowerEdge R710

Linux 2.6.18-92.el5 CentOS 5.2

load average: 1.39, 1.92, 4.95

MemTotal: 24675796 kB MemFree: 10980696 kB

Tags (2)
0 Karma

araitz
Splunk Employee
Splunk Employee
  • run your search in the "Advanced Charting" view rather than "Search" view
  • disable "Preview" checkbox
  • make sure you "Save" your search in the Jobs Manager
  • run "Search Profiler" to see where the bottlenecks are in your search

Stephen_Sorkin
Splunk Employee
Splunk Employee

These are all very good suggestions. In general, counting distinct counts are expensive as it requires storing every possible value of the field. What are the possible values for "date" here? Your search here will be faster if you run the search for every possible date value separately and then combine the results (perhaps by using a summary index).

0 Karma

bbingham
Builder

You could use a summary index for your IP and time fields. Populate the summary table at a set frequency, and then set your search to use the summary index as a source.

What are your goals in this search? Just a distinct IP for each day? min? second? Total hits?

0 Karma
Get Updates on the Splunk Community!

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...

Introducing the 2024 Splunk MVPs!

We are excited to announce the 2024 cohort of the Splunk MVP program. Splunk MVPs are passionate members of ...

Splunk Custom Visualizations App End of Life

The Splunk Custom Visualizations apps End of Life for SimpleXML will reach end of support on Dec 21, 2024, ...