Splunk sc4s
Splunk Connect for Syslog (SC4S) — all tasks. Trigger for: SC4S parser development, custom parsers, application blocks, block parsers, syslog-ng config, env_file, splunk_index.csv, sc4s-test, drop filters, routing, HEC configuration for SC4S, disk buffering, SC4S tuning, SC4S deployment, container pinning. Also trigger when the user pastes a raw syslog message destined for SC4S. Default: latest stable pinned SC4S release, RHEL/Rocky 8/9.From its SKILL.md
npx -y skills add cmwema/splunk-expert --skill splunk-sc4sAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.2 KB, as published. Nobody here has run it
Splunk Connect for Syslog (SC4S)
Router only. Read references/sc4s.md for all SC4S tasks.
Routing
| Task | Action |
|---|---|
| Parser development, env_file, routing, testing, tuning | Read references/sc4s.md |
| Raw syslog pasted for parsing | Identify format first (RFC 3164/5424/CEF/LEEF), then read references/sc4s.md |
Shared conventions
- All customization in
/opt/sc4s/local/— never touch files under/opt/sc4s/directly. - Pin container version:
ghcr.io/splunk/splunk-connect-for-syslog:<version>. Neverlatestin prod. - Enable disk buffering (
SC4S_DEST_SPLUNK_HEC_DEFAULT_DISKBUFF_ENABLE=yes) — required for HEC outage resilience. TLS_VERIFY=yesalways. Neververify=False.- Every parser sets
.splunk.sourcetype,fields.sc4s_vendor,fields.sc4s_product,fields.sc4s_vendor_product. sc4s_vendor_productmust be consistent across parser,splunk_index.csv, and the paired Splunk TA.- Drop filters go in early (
sc4s-postfilter) — kill noise before it reaches HEC. - Test every parser with
sc4s-testbefore deploying. - Never use the
defaultcatch-all sourcetype in production. - Pair every SC4S parser with a TA for CIM mapping at search time.
Syslog triage (quick)
Before writing config for a pasted log: identify format → propose sourcetype (vendor:product) → propose ingestion path (SC4S for syslog-over-wire, UF/HF inputs.conf for host files) → flag timestamp, event-breaking, and TZ issues.
Output format
Fenced syslog-ng blocks for parsers. bash for env_file. csv for splunk_index.csv. Section headers: SC4S Parser / env_file / splunk_index.csv / TA Notes / Best Practice Notes. Add ⚠️ Best Practice callouts. Flag data-loss and security implications.