Knowledge Management

Find the target indexer node responsible for causing indexqueue blocked across multiple source indexer nodes

hrawat
Splunk Employee
Splunk Employee
index=_internal source=*splunkd.log*  host=<all indexer hosts> bucketreplicator full earliest=-15m | stats count dc(host) as num_indexer_blocked_by_peer by peer | where num_indexer_blocked_by_peer > 0 AND count > 0 | join type=left peer [ search index=_introspection  host=<all indexer hosts> hostwide earliest=-10m | stats values(data.instance_guid) as peer by host]
Tags (1)

hrawat
Splunk Employee
Splunk Employee

Now (10.x onwards) you can find the time target blocked.

index=_internal bucketreplicator host=< all idx hosts> source=*splunkd.log*  total_blocked_time_seconds | timechart max(total_blocked_time_seconds) by peer

index=_internal bucketreplicator host=< all idx hosts> source=*splunkd.log*  total_blocked_time_seconds | timechart max(total_blocked_time_seconds) by bid
Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Dynamic formatting from XML events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  &#x1f680; Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Stronger Security with Federated Search for S3, GCP SQL & Australian Threat ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...