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!

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...

Tech Talk | Elevating Digital Service Excellence: The Synergy of Splunk RUM & APM

Elevating Digital Service Excellence: The Synergy of Real User Monitoring and Application Performance ...