splunk-configure

Generate Splunk Observability Cloud detector Terraform from otel-audit reports.

12|8|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/signalfx/obstudio --skill splunk-configure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: splunk-configure
Source: https://github.com/signalfx/obstudio/tree/main/skills/splunk-configure
Command: npx skills add https://github.com/signalfx/obstudio --skill splunk-configure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill converts an existing otel-audit report into ready-to-apply Splunk Observability Cloud detector Terraform, so you can move from “what’s missing” to “what should alert” faster.

Core Features & Use Cases

  • Classifies metrics into detector categories: Maps latency, error, throughput, and saturation signals from the audit report into the appropriate monitoring approach.
  • Generates Terraform + SignalFlow: Produces .observe/terraform/detectors.tf with signalfx_detector resources and inline SignalFlow program_text.
  • Creates supporting Terraform files and documentation: Writes .observe/terraform/variables.tf, .observe/terraform/terraform.tfvars.example, and a human-readable .observe/detectors.md explaining decisions and skips.
  • Safety checks and guardrails: Stops early with clear guidance if .observe/otel.md is missing or if the audit report contains no detected metrics.

Quick Start

Run cp to copy the generated .observe/terraform/terraform.tfvars.example to .observe/terraform/terraform.tfvars, fill in realm, api_token, and notification_channel, then apply the Terraform in .observe/terraform.

Frequently Asked Questions about splunk-configure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Splunk Observability Cloud detectors from an otel-audit report?

To generate Splunk Observability Cloud detectors, the Skill reads your existing otel-audit report, classifies latency, error, throughput, and saturation metrics, and emits Terraform HCL files with inline SignalFlow into the .observe/terraform directory.

What is the best way to create Terraform for Splunk detectors using infrastructure as code?

Creating Terraform for Splunk detectors is handled by mapping audited metrics into detector categories, producing a detectors.tf file with signalfx_detector resources and inline SignalFlow program_text, alongside supporting variables.tf and tfvars.example files.

Do I need an otel-audit report to generate Splunk detector Terraform?

Yes, you need an otel-audit report and a .observe/otel.md file to generate Splunk detector Terraform. The Skill stops early with clear guidance if the otel.md file is missing or if the audit report contains no detected metrics.

How does metric classification work for Splunk Observability Cloud detectors?

Metric classification for Splunk detectors works by categorizing latency, error, throughput, and saturation signals from the audit report into appropriate monitoring approaches, then generating corresponding SignalFlow programs and Terraform resources.

What files are generated when converting audit findings to Splunk detectors?

Converting audit findings to Splunk detectors generates detectors.tf with signalfx_detector resources, variables.tf, terraform.tfvars.example in the .observe/terraform directory, and a companion detectors.md report explaining decisions and skips.

Why does my Splunk detector Terraform generation stop early with an error?

Splunk detector Terraform generation stops early if the .observe/otel.md file is missing from the repository or if the otel-audit report contains no detected metrics, providing clear guidance on what is required to proceed.