Skip to main content
User guide

Platform health

An eight-point Splunk check-up with AI interpretation. The slow-search advisor finds the most expensive searches in _audit, rewrites them, verifies by result count on real data and applies them to the saved search.

Platform health is the first page of Administration; its tab family includes Audit log and Outbound channels, with a Search performance tab inside the page. The check-up is in every edition; interpretation is a paid capability.

Check-up

Check-up

Eight checks, each ok, warn, fail or unknown with summary, evidence and advice. Thresholds are set in [platform].

CheckLooks atSource
splunkd healthYellow or red features in the health tree and their reasons/services/server/health/splunkd/details
Indexer clusterCluster state. A standalone instance is ok/services/cluster/manager/info
Licence usagePool usage percentage, warning count (5 is fail)/services/licenser/pools
Internal error rate24-hour log_level=ERROR by componentindex=_internal
Scheduler skipsSkip ratio, most-skipped saved searches and reasonsindex=_internal sourcetype=scheduler
KV storeStatus/services/kvstore/status
Ingest freshnessAge of each sourcetype's newest event (fewer than 100 events ignored)| metadata type=sourcetypes
Clock baselineEvent time ahead of now (collector clock skew)Same

A user without read access to licenser or cluster sees those checks as unknown. Under a Splunk Free licence the cluster endpoint returns 402 and is unknown too.

AI interpretation

Interpret hands the eight results to the model, which links related failures (two log types stopping in the same second points at the upstream collection path) and returns a conclusion plus actions[{title, why, how}] where how is read-only SPL. Matching runbooks from the knowledge base enter the prompt. 25 to 32 s on the 1.9.0 test box.

Interpretation

Search performance

From 1.8.0, the Search performance tab pulls the last 7 days of completed searches from _audit (action=search info=completed), excludes this app's own, DMC housekeeping and splunk-system-user, and ranks the Top 20 by total run time:

ColumnNotes
SearchSPL fragment
Runs / total timeOver 7 days
Scan efficiencyevent_count / scan_count; lower is more wasteful
SourceThe saved search. Required before a rewrite can be applied

Slow searches

Optimize on a row: the model returns optimized_spl, expected_gain, why and risk; both SPLs are syntax-checked with | head 0 and compared with | stats count ([spl_advisor] verify_window, default -24h), and verified states whether the counts match. Typical rewrite: index=* | stats count by host becomes index=rst_demo | fields host | stats count by host.

Rewrite advice

Apply to saved search (admin) replaces its search field after a KV backup (copilot_state kind advisor_backup); Revert on the row restores it. Only searches applied from this page have a backup; anything else returns advisor_no_backup. The 2^64-scale total_run_time that _audit writes for cancelled or zombie jobs is filtered out.

On this page