Splunk Ingest Processor Setup
Prerequisites
| Tool or access |
Purpose |
Verify |
| Bash and Python 3 |
Run bundled setup and validation helpers |
bash --version && python3 --version |
| Required product/platform access |
Inspect or configure the selected target |
Complete the documented preflight |
| Credential files for live modes |
Keep secrets out of chat |
Verify paths only |
Workflow Overview
┌───────────┐ ┌───────────────┐ ┌───────────────┐ ┌─────────────────┐
│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │
└───────────┘ └───────────────┘ └───────────────┘ └─────────────────┘
When to Activate
- Configure Ingest Processor, author Ingest Processor pipelines, route or transform data at ingest time, validate
Ingest Processor readiness, or compare Ingest Processor with Edge Processor and Data Manager, including Cisco Data
Fabric or.
- Preview and review the splunk ingest processor setup workflow before any live apply phase.
- Diagnose failed prerequisites, generated assets, configuration, or validation evidence.
Scope
Follow the documented read-only or render-first path whenever it is available.
This skill does not imply permission to mutate live systems. Require explicit
apply flags, protected credentials, and operator review for state changes.
Examples
Inspect the supported setup modes before selecting one:
bash skills/splunk-ingest-processor-setup/scripts/setup.sh --help
Expected output: usage, supported modes, and required arguments are displayed
without changing the target environment.
Inspect validation modes before running completion checks:
bash skills/splunk-ingest-processor-setup/scripts/validate.sh --help
Expected output: offline, live, and completion options are displayed when the
skill supports them; help exits without mutation.
Troubleshooting
| Issue |
Cause |
Resolution |
| Preflight fails |
A required tool or access path is missing |
Resolve it before rendering or applying |
| Rendered assets are incomplete |
Required non-secret inputs are absent |
Complete intake and render again |
| Apply is blocked |
Review, credentials, or explicit acceptance is missing |
Use the documented handoff |
| Validation is incomplete |
Live evidence is unavailable |
Record the gap and keep completion open |
This skill is a render-first workflow for Splunk Cloud Platform Ingest
Processor. It prepares the complete operator packet for IP readiness,
source-type and destination setup, SPL2 pipeline authoring, monitoring, and
post-ingest data usability.
For newer Cisco Data Fabric wording, this is the Splunk Cloud ingest-time
pipeline route. Keep native Observability Metrics Pipeline Management requests
in splunk-observability-deep-native-workflows unless the user needs
source-type, destination, or SPL2 pipeline assets.
Agent Behavior
- Do not claim private or undocumented Ingest Processor CRUD APIs. The apply
path is a UI/support handoff unless Splunk publishes a stable public API.
- Keep credentials out of chat and rendered files. Use local chmod 600 files
for HEC tokens, Observability access tokens, cloud keys, and private keys.
- Use
splunk-spl2-pipeline-kit for SPL2 templates and compatibility linting.
- Hand off Splunk Enterprise destinations to
splunk-edge-processor-setup;
Ingest Processor destinations are Splunk Cloud, Observability Cloud, metrics
indexes, and Amazon S3.
- Hand off post-ingest ES/ITSI/ARI/CIM/OCSF/dashboard validation to
splunk-data-source-readiness-doctor when that skill is present.
- Read
reference.md before changing coverage, limits, or lifecycle behavior.
- Treat AI-powered Data Management release stages as capability-specific:
Automated Field Extraction was announced in Controlled Availability, while
Guided Onboarding with Auto-Schematization was announced in Alpha. Both were
announced 2026-03-11 and re-checked 2026-08-20 against the Ingest Processor
release notes updated 2026-06-16, which promote neither capability; see
references/research-ledger.md for the recorded negative evidence. Verify
current tenant access before presenting either workflow. The announcement
says three capabilities but publicly names only these two; do not infer a
third capability.
Quick Start
Render a complete offline packet:
bash skills/splunk-ingest-processor-setup/scripts/setup.sh \
--phase all \
--tenant-name acme-prod \
--stack-url https://acme-prod.scs.splunk.com \
--source-types "aws:cloudtrail,crowdstrike:fdr,json_app" \
--destinations "splunk_indexer=type=splunk_cloud;default=true,metrics=type=metrics_index;index=metrics,s3_archive=type=s3;format=parquet;bucket=example-bucket" \
--pipelines "redact_auth=template=redact;sourcetype=json_app;destination=splunk_indexer,http_metrics=template=metrics;destination=metrics"
--phase accepts render, doctor, status, validate, and all. Because
Ingest Processor exposes no public REST API for live status, doctor and
status are offline aliases of validate (render plus structural validation);
they do not query a live tenant.
--dry-run parses and reports the complete plan without creating, deleting, or
rewriting the output directory. Refused destinations (including Splunk
Enterprise/HEC targets and S3 Object Lock) emit their concrete handoff and
return nonzero in every phase; a rendered handoff is not a successful setup.
Normal rendering replaces only an empty directory or one carrying this skill's
ownership marker/legacy README; it refuses to recursively delete an unrelated
nonempty path.
Validate the skill offline:
bash skills/splunk-ingest-processor-setup/scripts/validate.sh
Outputs
The default output directory is splunk-ingest-processor-rendered/:
readiness-report.md and coverage-report.json.
apply-plan.json with ui_handoff actions only.
source-types/*.json, destinations/*.json, and pipelines/*.spl2.
spl2-pipeline-kit/ rendered by splunk-spl2-pipeline-kit.
monitoring/searches.spl and monitoring/usage-summary-handoff.md.
control-plane-handoffs/ai-powered-data-management.md with current
availability, access, review, and no-automation guardrails.
lifecycle/*.md for apply, edit, remove, refresh, delete, and rollback
review.
handoffs/*.md for HEC, Edge Processor, S3 Federated Search, and data-source
readiness workflows.
Coverage Rules
- Ingest Processor is Splunk Cloud Platform Victoria Experience only.
- Verify provisioning, subscription/tier, roles, service account access,
indexes, lookups, and connection refresh before authoring pipelines.
- Confirm default destination behavior in the UI before applying a pipeline.
- Validate source-type event breaking, sample data, and preview results before
apply.
- Treat Automated Field Extraction as a Controlled Availability,
region-gated UI suggestion workflow, not an API automation path. Verify
tenant entitlement and current feature visibility before use. Announced
2026-03-11, re-checked 2026-08-20: the release notes updated 2026-06-16 list
AFE under February 18, 2026 with no release-stage label, label other
features "(Controlled Availability release)" and "(General Availability
release)" inline when those stages apply, and never state that AFE is
generally available.
- Treat Guided Onboarding with Auto-Schematization as an Alpha, enrollment-
gated UI workflow. It can recommend CIM mappings and candidate TA or SPL2
outputs, but this skill does not invoke the service, enroll a tenant,
generate a TA, install a TA, or apply a generated pipeline. Announced
2026-03-11, re-checked 2026-08-20: the release notes updated 2026-06-16
contain no Auto-Schematization or Guided Onboarding entry, which is equally
consistent with still-Alpha and with withdrawal, so the Alpha stance holds.
- Require human review, SPL2 lint/preview, representative sample validation,
CIM validation, and an explicit apply decision for every AI-generated
recommendation or artifact.
- Treat decrypt as a private-key lookup workflow and warn about throughput.
- Treat S3 Object Lock as unsupported for rendered IP destination plans.
- Render and review known issue guardrails: tenant-admin-only editing, no data
delivery guarantees under high back pressure or destination outages,
single-browser-session editing, forwarder
useACK=false, HEC indexer
acknowledgement off, and CIDR lookup matching unsupported.
1---2name: splunk-ingest-processor-setup3description: "Use when the user asks to configure Ingest Processor, author Ingest Processor pipelines, route or4 transform data at ingest time, validate Ingest Processor readiness, or compare Ingest Processor with5 Edge Processor and Data Manager, including Cisco Data Fabric or telemetry pipeline management requests6 that involve Splunk Cloud ingest-time routing and transformation. Render Cisco Data Fabric ingest-time7 routing workflows and Splunk Cloud Platform Ingest Processor setup plans with SPL2 pipelines, source8 types, destinations, lifecycle handoffs, queue and monitoring searches, metrics, OCSF, decrypt, S39 archive, custom pipeline templates, AI-powered data management readiness, Automated Field Extraction,10 Guided Onboarding with Auto-Schematization, and downstream readiness checks."11compatibility: "Splunk Cloud Platform 10.5.2605: conditional. Follow documented package, entitlement, topology, and customer-managed runtime guardrails; self-managed paths remain on the public 10.4 baseline."12metadata:13 source: https://skillmd.com/skills/chambear2809/splunk-ingest-processor-setup14 splunk_cloud_10_5: "conditional"15 compatibility_verified: "2026-08-20"16---1718# Splunk Ingest Processor Setup1920## Prerequisites2122| Tool or access | Purpose | Verify |23|---|---|---|24| Bash and Python 3 | Run bundled setup and validation helpers | `bash --version && python3 --version` |25| Required product/platform access | Inspect or configure the selected target | Complete the documented preflight |26| Credential files for live modes | Keep secrets out of chat | Verify paths only |2728## Workflow Overview2930```text31┌───────────┐ ┌───────────────┐ ┌───────────────┐ ┌─────────────────┐32│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │33└───────────┘ └───────────────┘ └───────────────┘ └─────────────────┘34```3536## When to Activate3738- Configure Ingest Processor, author Ingest Processor pipelines, route or transform data at ingest time, validate39 Ingest Processor readiness, or compare Ingest Processor with Edge Processor and Data Manager, including Cisco Data40 Fabric or.41- Preview and review the splunk ingest processor setup workflow before any live apply phase.42- Diagnose failed prerequisites, generated assets, configuration, or validation evidence.4344## Scope4546Follow the documented read-only or render-first path whenever it is available.47This skill does not imply permission to mutate live systems. Require explicit48apply flags, protected credentials, and operator review for state changes.4950## Examples5152Inspect the supported setup modes before selecting one:5354```bash55bash skills/splunk-ingest-processor-setup/scripts/setup.sh --help56```5758Expected output: usage, supported modes, and required arguments are displayed59without changing the target environment.6061Inspect validation modes before running completion checks:6263```bash64bash skills/splunk-ingest-processor-setup/scripts/validate.sh --help65```6667Expected output: offline, live, and completion options are displayed when the68skill supports them; help exits without mutation.6970## Troubleshooting7172| Issue | Cause | Resolution |73|---|---|---|74| Preflight fails | A required tool or access path is missing | Resolve it before rendering or applying |75| Rendered assets are incomplete | Required non-secret inputs are absent | Complete intake and render again |76| Apply is blocked | Review, credentials, or explicit acceptance is missing | Use the documented handoff |77| Validation is incomplete | Live evidence is unavailable | Record the gap and keep completion open |7879This skill is a render-first workflow for Splunk Cloud Platform Ingest80Processor. It prepares the complete operator packet for IP readiness,81source-type and destination setup, SPL2 pipeline authoring, monitoring, and82post-ingest data usability.8384For newer Cisco Data Fabric wording, this is the Splunk Cloud ingest-time85pipeline route. Keep native Observability Metrics Pipeline Management requests86in `splunk-observability-deep-native-workflows` unless the user needs87source-type, destination, or SPL2 pipeline assets.8889## Agent Behavior9091- Do not claim private or undocumented Ingest Processor CRUD APIs. The apply92 path is a UI/support handoff unless Splunk publishes a stable public API.93- Keep credentials out of chat and rendered files. Use local chmod 600 files94 for HEC tokens, Observability access tokens, cloud keys, and private keys.95- Use `splunk-spl2-pipeline-kit` for SPL2 templates and compatibility linting.96- Hand off Splunk Enterprise destinations to `splunk-edge-processor-setup`;97 Ingest Processor destinations are Splunk Cloud, Observability Cloud, metrics98 indexes, and Amazon S3.99- Hand off post-ingest ES/ITSI/ARI/CIM/OCSF/dashboard validation to100 `splunk-data-source-readiness-doctor` when that skill is present.101- Read `reference.md` before changing coverage, limits, or lifecycle behavior.102- Treat AI-powered Data Management release stages as capability-specific:103 Automated Field Extraction was announced in Controlled Availability, while104 Guided Onboarding with Auto-Schematization was announced in Alpha. Both were105 announced 2026-03-11 and re-checked 2026-08-20 against the Ingest Processor106 release notes updated 2026-06-16, which promote neither capability; see107 `references/research-ledger.md` for the recorded negative evidence. Verify108 current tenant access before presenting either workflow. The announcement109 says three capabilities but publicly names only these two; do not infer a110 third capability.111112## Quick Start113114Render a complete offline packet:115116```bash117bash skills/splunk-ingest-processor-setup/scripts/setup.sh \118 --phase all \119 --tenant-name acme-prod \120 --stack-url https://acme-prod.scs.splunk.com \121 --source-types "aws:cloudtrail,crowdstrike:fdr,json_app" \122 --destinations "splunk_indexer=type=splunk_cloud;default=true,metrics=type=metrics_index;index=metrics,s3_archive=type=s3;format=parquet;bucket=example-bucket" \123 --pipelines "redact_auth=template=redact;sourcetype=json_app;destination=splunk_indexer,http_metrics=template=metrics;destination=metrics"124```125126`--phase` accepts `render`, `doctor`, `status`, `validate`, and `all`. Because127Ingest Processor exposes no public REST API for live status, `doctor` and128`status` are offline aliases of `validate` (render plus structural validation);129they do not query a live tenant.130131`--dry-run` parses and reports the complete plan without creating, deleting, or132rewriting the output directory. Refused destinations (including Splunk133Enterprise/HEC targets and S3 Object Lock) emit their concrete handoff and134return nonzero in every phase; a rendered handoff is not a successful setup.135Normal rendering replaces only an empty directory or one carrying this skill's136ownership marker/legacy README; it refuses to recursively delete an unrelated137nonempty path.138139Validate the skill offline:140141```bash142bash skills/splunk-ingest-processor-setup/scripts/validate.sh143```144145## Outputs146147The default output directory is `splunk-ingest-processor-rendered/`:148149- `readiness-report.md` and `coverage-report.json`.150- `apply-plan.json` with `ui_handoff` actions only.151- `source-types/*.json`, `destinations/*.json`, and `pipelines/*.spl2`.152- `spl2-pipeline-kit/` rendered by `splunk-spl2-pipeline-kit`.153- `monitoring/searches.spl` and `monitoring/usage-summary-handoff.md`.154- `control-plane-handoffs/ai-powered-data-management.md` with current155 availability, access, review, and no-automation guardrails.156- `lifecycle/*.md` for apply, edit, remove, refresh, delete, and rollback157 review.158- `handoffs/*.md` for HEC, Edge Processor, S3 Federated Search, and data-source159 readiness workflows.160161## Coverage Rules162163- Ingest Processor is Splunk Cloud Platform Victoria Experience only.164- Verify provisioning, subscription/tier, roles, service account access,165 indexes, lookups, and connection refresh before authoring pipelines.166- Confirm default destination behavior in the UI before applying a pipeline.167- Validate source-type event breaking, sample data, and preview results before168 apply.169- Treat Automated Field Extraction as a Controlled Availability,170 region-gated UI suggestion workflow, not an API automation path. Verify171 tenant entitlement and current feature visibility before use. Announced172 2026-03-11, re-checked 2026-08-20: the release notes updated 2026-06-16 list173 AFE under February 18, 2026 with no release-stage label, label other174 features "(Controlled Availability release)" and "(General Availability175 release)" inline when those stages apply, and never state that AFE is176 generally available.177- Treat Guided Onboarding with Auto-Schematization as an Alpha, enrollment-178 gated UI workflow. It can recommend CIM mappings and candidate TA or SPL2179 outputs, but this skill does not invoke the service, enroll a tenant,180 generate a TA, install a TA, or apply a generated pipeline. Announced181 2026-03-11, re-checked 2026-08-20: the release notes updated 2026-06-16182 contain no Auto-Schematization or Guided Onboarding entry, which is equally183 consistent with still-Alpha and with withdrawal, so the Alpha stance holds.184- Require human review, SPL2 lint/preview, representative sample validation,185 CIM validation, and an explicit apply decision for every AI-generated186 recommendation or artifact.187- Treat decrypt as a private-key lookup workflow and warn about throughput.188- Treat S3 Object Lock as unsupported for rendered IP destination plans.189- Render and review known issue guardrails: tenant-admin-only editing, no data190 delivery guarantees under high back pressure or destination outages,191 single-browser-session editing, forwarder `useACK=false`, HEC indexer192 acknowledgement off, and CIDR lookup matching unsupported.