splunk-servicenow-ta-setup

Splunk Add-on for ServiceNow Setup

Prerequisites

Workflow Overview

┌───────────┐   ┌───────────────┐   ┌───────────────┐   ┌─────────────────┐
│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │
└───────────┘   └───────────────┘   └───────────────┘   └─────────────────┘

When to Activate

• Splunk_TA_snow, the Splunk Add-on for ServiceNow, ServiceNow incident or change or CMDB ingestion, snow:// inputs, or ITSM data onboarding in Splunk.
• Preview and review the splunk servicenow ta 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-servicenow-ta-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-servicenow-ta-setup/scripts/validate.sh --help

Expected output: offline, live, and completion options are displayed when the skill supports them; help exits without mutation.

Troubleshooting

TA Completion Gate

For every TA/add-on or dashboard companion run, satisfy the shared TA completion gate: configure and enable the data ingest path owned by this skill or its required companion, validate events or metrics in the target indexes/source types, and verify any pre-built/package-shipped dashboards are visible, macro-aligned, and returning data. If the package ships no dashboards, record that evidence explicitly and hand off dashboard use to the consuming app, ES/ITSI/ARI content, or readiness doctor.

Render-first automation for the Splunk Add-on for ServiceNow (Splunk_TA_snow, Splunkbase 1928). The add-on pulls ServiceNow table records through the REST API; each snow://<table> input emits the snow:<table> source type.

The add-on runs on the search tier or a heavy forwarder. Run a given table input on a single node to avoid duplicate collection.

Package Verification Boundary

This skill's package-derived inputs and handlers were verified against 10.0.1. The current public release is 11.0.0 and advertises Splunk 10.5 support, but its package contents have not been verified by this repository. The shared installer defaults to verified 10.0.1; only --accept-unverified-release follows public 11.0.0. After that explicit override, inspect its input/account schema and repeat the completion-gate validation before applying these templates.

Tables And Source Types

Credentials

Never paste a ServiceNow password or OAuth secret in chat or argv. Use a read-only integration user. Write the secret to a local file and configure the account in the add-on Configuration tab:

bash skills/shared/scripts/write_secret_file.sh /tmp/snow_password

See the rendered account-setup.md for both basic-auth and OAuth modes.

Workflow

1. Render reviewable assets (offline):

bash skills/splunk-servicenow-ta-setup/scripts/setup.sh --render \
  --index snow --account-name snow_prod --tables incident,change_request,problem,em_event

2. Install the add-on and create the index:

bash skills/splunk-servicenow-ta-setup/scripts/setup.sh --install --create-index --index snow

3. Configure the account (account-setup.md) and enable the rendered inputs.

4. Validate:

bash skills/splunk-servicenow-ta-setup/scripts/validate.sh --index snow

ServiceNow incident/change data is commonly consumed by Splunk ITSI; hand off service and KPI modeling to splunk-itsi-config. See reference.md for the full input/account model, checkpointing, source types, and placement guardrails.