Splunk Enterprise

Regex Processor CPU Profiling per Sourcetype” under "DMC -> Indexing -> Indexing Performance:Instances" is not populating any data.

khusain_splunk
Splunk Employee
Splunk Employee

Regex Processor CPU Profiling per Sourcetype” under "DMC -> Indexing -> Indexing Performance:Instances" is not populating any data.

Tags (1)
1 Solution

mbagali_splunk
Splunk Employee
Splunk Employee

“Regex Processor CPU Profiling per Sourcetype” is a new splunk feature and by default this panel do not populate any data.

To load the panel we need to set "regex_cpu_profiling = true" in limits.conf file. By default it is set to false.

regex_cpu_profiling =

* Enable CPU time metrics for RegexProcessor. Output will be in the
metrics.log file.
Entries in metrics.log will appear per_host_regex_cpu, per_source_regex_cpu,
per_sourcetype_regex_cpu, per_index_regex_cpu.
* Default: false

"regex_cpu_profiling" is utilized as a troubleshooting tool to identify blocks in the typing queue and narrowing down which source and/or source type is taking most of the CPU time or the CPU time per event.

If you are interested in the per_host_regex_cpu it would be necessary to enable the regex_cpu_profiling = true on all of the "Indexers" so you can receive these type of metrics logs from all the indexers.

We recommend you compare splunkd CPU utilization before & after turning it on.

View solution in original post

mbagali_splunk
Splunk Employee
Splunk Employee

“Regex Processor CPU Profiling per Sourcetype” is a new splunk feature and by default this panel do not populate any data.

To load the panel we need to set "regex_cpu_profiling = true" in limits.conf file. By default it is set to false.

regex_cpu_profiling =

* Enable CPU time metrics for RegexProcessor. Output will be in the
metrics.log file.
Entries in metrics.log will appear per_host_regex_cpu, per_source_regex_cpu,
per_sourcetype_regex_cpu, per_index_regex_cpu.
* Default: false

"regex_cpu_profiling" is utilized as a troubleshooting tool to identify blocks in the typing queue and narrowing down which source and/or source type is taking most of the CPU time or the CPU time per event.

If you are interested in the per_host_regex_cpu it would be necessary to enable the regex_cpu_profiling = true on all of the "Indexers" so you can receive these type of metrics logs from all the indexers.

We recommend you compare splunkd CPU utilization before & after turning it on.

gjanders
SplunkTrust
SplunkTrust

This does not appear to be well documented but I believe you can enable it in the limits.conf file:

regex_cpu_profiling = <bool>
* Enable CPU time metrics for RegexProcessor. Output will be in the 
  metrics.log file.
  Entries in metrics.log will appear per_host_regex_cpu, per_source_regex_cpu,
  per_sourcetype_regex_cpu, per_index_regex_cpu.
* Default: false

The help page for the monitoring console goes here but no mention of the above setting...

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...