splunk-observability-isovalent-integration

To wire Cilium and Tetragon telemetry into Splunk Observability Cloud, you can render a Splunk OTel Collector overlay with Prometheus scrape jobs, metric filters, and file-based ingestion defaults to apply to your cluster.

Configuring Splunk OTel Collector to scrape Hubble metrics is done by rendering an overlay with seven Prometheus scrape jobs and a strict metric allow-list to filter telemetry from Hubble and other Isovalent components.

Yes, shipping Tetragon logs to Splunk Platform is supported through generated handoff scripts for HEC ingestion, alongside file-based ingestion defaults and stdout paths for Tetragon telemetry.

Yes, you can use fluentd for Isovalent log ingestion with Splunk through deprecated fluentd paths supported by the integration, alongside file-based and stdout ingestion methods for telemetry.

Validating Tetragon ingestion with hostPath coordination requires token-safety checks and a set of validation steps across the workflow to ensure proper file-based log ingestion into Splunk.

Generating Splunk dashboards and detectors for Cilium metrics is handled by the integration, which produces handoff scripts for base collector, HEC, and Cisco Security Cloud ingestion alongside the telemetry overlays.