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!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...

Watch On Demand the Tech Talk on November 6 at 11AM PT, and empower your SOC to reach new heights! Duration: ...

Splunk Observability as Code: From Zero to Dashboard

For the details on what Self-Service Observability and Observability as Code is, we have some awesome content ...