Monitoring Splunk

Why does this _internal log message have two similar key=value pairs and can this be changed?

rkursawe
Explorer

It's not really a question, but could you please change your _internal log message:

The maximum number of concurrent scheduled searches has been reached (limits: historical=2, realtime=2). historical=21, realtime=0 ready-to-run scheduled searches are pending.

I have to add a regular expression to get the interesting historical value.

0 Karma

rkursawe
Explorer

Only if someone has the same problem. I used this regex in order to get the value from the second historical pair.

| rex field=_raw "). historical=(?\d+)"

0 Karma

s2_splunk
Splunk Employee
Splunk Employee

Please feel free to submit an enhancement request via the Splunk support portal .

0 Karma
Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

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