Five lessons, in order
Each builds on the last. Detectors carry the most weight, so they get the most time. Your practice scores save on this device.
Each lesson stands on the one before. Lesson 4 is over a third of the test. Your scores save on this device.
Metrics concepts
The data model, rollups and metadata.
Postcards, diaries, sticky notes and meters.
StartCharts and built-in content
Metric Finder, chart types, dashboards, built-in content, alert subscriptions.
Turning diaries into pictures; using the dashboards Splunk already made.
StartAnalytics
Aggregations, transformations, formulas, timeshift, moving and calendar windows.
Math on charts: add it up, compare to last week, make percentages.
StartDetectors and alerts
Detectors, alert conditions, muting, non-flapping alerts, populations, late data.
Smoke alarms that go off for real problems and stay quiet otherwise.
StartData in and Kubernetes
The OTel Collector on Linux and its config; Kubernetes Navigator and analyzer.
Installing the mail carrier on a server; the map of your Kubernetes cluster.
StartWhere the 58 questions come from
Eight domains, weighted by their share of the exam. Select one to see what it covers.
Think of the exam as a pizza cut into 8 uneven slices. Bigger slice, more questions. Pick a slice to see what's on it.
A full mock exam
58 questions in 60 minutes, drawn to match the blueprint weights, with no feedback until you submit. Results break down by domain so you know what to reread.
A dress rehearsal: same number of questions, same clock, same mix of topics. You only see the answers at the end, like the real thing.
Send your own data
The labs use a small shell script that posts hand-made datapoints to the ingest API, so you can watch MTS, rollups, analytics and detectors react to data you control. It needs an org access token with ingest scope, saved to a file only you can read.
The labs come with a tiny script that mails made-up postcards to your Splunk account, so you can see exactly what happens to them. You give it a key once and it does the rest.
mkdir -p ~/.config/splunk-o11y pbpaste > ~/.config/splunk-o11y/ingest-token # copy the token first chmod 600 ~/.config/splunk-o11y/ingest-token REALM=us1 ./send.sh test
Set REALM to your org's realm (it's in the URL, like app.us1.observability...). The token is read from the file and passed to curl on stdin, never on the command line.