Splunk’s September 18, 2026 announcement states that Cisco completed its acquisition of Galileo and presents Agent Observability as the resulting offering. Future-tense feature announcements are not treated as current availability.
Inspect the evidence ↘GOVERNATLAS / PRODUCT DOSSIER
Splunk Agent Observability
Splunk documents Agent Observability as an observability, evaluation and guardrail offering with on-premises and Splunk Observability Cloud SaaS deployment options. Current documentation explicitly says features/configuration vary by deployment; legacy Galileo onboarding scope is separate.
THE DOCUMENTED SCOPE
What the current evidence describes.
Source-attributed capabilities and limits. Inspect the full record before drawing a conclusion.
01 / CONTEXT & SCOPE
Understand the proposition.
Define the boundary.
The decision to make
Treat this as one successor product identity rather than a new listing beside Galileo. New-customer evaluation should use current Splunk documentation, while existing Galileo customers must establish their migration and contractual scope separately. Pick the operating model before comparing evaluators, SDKs and guardrails.
What this record does not establish
The preserved legacy banner limits those docs to customers onboarded before August 7, 2026. Current Splunk docs and its completed-acquisition announcement resolve the naming hold; announced future Luna capabilities are not treated as generally available. No blanket deployment parity or evaluation accuracy is independently established.
2 current sources · 2 published assertions
Source coverage is a research boundary, not a quality score.
Source coverage is a research boundary, not a quality score.
02 / YOUR EVALUATION
Turn interest into a useful trial.
A
A test worth running
In a proposed pilot, log a model/tool trace, evaluate a known failure and compare an experiment revision. Inspect where the evaluator runs and what a configured runtime intervention changes for the caller. Compare the proposed SaaS or on-premises feature matrix, retaining missing functionality and migration questions as open decisions.
GovernAtlas editorial proposal. We have not performed this test.
B
Evidence to bring back
- A legacy-to-current identity/migration record and dated deployment feature matrix.
- A trace/evaluation/experiment record with evaluator location and runtime outcome.
03 / DOCUMENTED EVIDENCE
Read the claim. Inspect the basis.
Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.
vendor asserted
Splunk’s September 18, 2026 announcement states that Cisco completed its acquisition of Galileo and presents Agent Observability as the resulting offering. Future-tense feature announcements are not treated as current availability.
Source, dates & preserved provenance
Splunk — Observe, Evaluate, and Guardrail Your AI Agents ↗Authority: vendor owned
Observed 2026-10-15 · Reviewed 2026-10-15 · current until 2026-11-14
Artifact SHA-256: 60bf201d95deec9343daeb94cf515a03fca9be3516d8db80ec2c336627c093ed
The hash identifies the preserved capture. The live source may have changed.
vendor asserted
Splunk documents Agent Observability as an observability, evaluation and guardrail offering with on-premises and Splunk Observability Cloud SaaS deployment options. Current documentation explicitly says features/configuration vary by deployment; legacy Galileo onboarding scope is separate.
Source, dates & preserved provenance
Splunk Agent Observability — current product documentation ↗Authority: vendor owned
Observed 2026-10-15 · Reviewed 2026-10-15 · current until 2026-11-14
Artifact SHA-256: 9debbe4cbe1249f14cdeec2ef25aa4b80b8986671711b6492feb0954f7fd047f
The hash identifies the preserved capture. The live source may have changed.
Source register
Splunk — Observe, Evaluate, and Guardrail Your AI Agents ↗vendor owned · captured 2026-10-15
Splunk Agent Observability — current product documentation ↗vendor owned · captured 2026-10-15
Brand asset provenance
Organization identity asset from its official website; inclusion does not imply endorsement.
Official website ↗ · Original asset ↗04 / BEFORE YOU COMMIT
Better questions.
A clearer decision.
Resolve these with the provider and your own evaluation team.
A legacy-to-current identity/migration record and dated deployment feature matrix. Can this be supplied for the proposed configuration?
A trace/evaluation/experiment record with evaluator location and runtime outcome. Can this be demonstrated in a sandbox?
Which migration, support and contract conditions apply to an existing Galileo customer?
Regulatory applicability requires a separate, current determination. Inclusion is not certification.
KEEP THE RECORD USEFUL
A dossier should stand up to scrutiny.
Have a source that changes this picture? Submit it for editorial review.