Skip to main content
The Splunk Agent Observability integration connects Luna Studio to the rest of the Splunk Agent Observability platform. The Integrations page lets a user save a personal galileo_api record and an administrator save a workspace-scoped record. In the current release, however, dataset import and evaluator registration do not read either in-app record. Those operations instead read the Splunk Agent Observability API URL and key from deployment settings for the Luna Studio backend.
This is a current-release runtime limitation, not a permanent deployment-only architecture. Saving or successfully testing either a personal or workspace Splunk Agent Observability card does not make those credentials available to dataset import or evaluator registration.

​
When you need it

The Splunk Agent Observability integration unlocks two platform features:
  • Import from Splunk Agent Observability — pull datasets from your Splunk Agent Observability workspace into Luna Studio. Available when adding a dataset and in Step 2 and Step 3 of the run creation flow.
  • Register evaluator — publish an eligible fine-tuned evaluator from Luna Studio into the Splunk Agent Observability evaluators store, where it becomes available across evaluation, observability, and guardrails. See Register an evaluator.
You can use Luna Studio without the Splunk Agent Observability integration — uploads, URL fetches, and local-only flows work fine — but registration and Splunk Agent Observability-sourced data require it.

​
Configure the effective connection in the current release

1

Ask your deployment operator

The operator must configure both the Splunk Agent Observability API URL and API key for the Luna Studio backend. The backend-native environment names are LUNA_GALILEO_API_URL and LUNA_GALILEO_API_KEY. The Luna fine-tuning SDK aliases GALILEO_API_URL and GALILEO_API_KEY are also accepted, allowing the backend and fine-tuning SDK to use the same deployment values.
2

Verify the consuming flows

To verify dataset access, select Import from Splunk Agent Observability while adding a dataset. To verify registration, open an eligible run with the Fine-tuned status and inspect its Register evaluator action; the run-details preflight reports missing Splunk Agent Observability settings and other registration blockers. Do not rely on the Splunk Agent Observability card’s saved or tested state to verify these flows in the current release.
These are literal Luna backend identifiers retained by the current implementation. They are separate from the public splunk-ao-python application settings: SPLUNK_AO_API_KEY, SPLUNK_AO_CONSOLE_URL, and the optional SPLUNK_AO_API_URL. Setting the public SDK variables does not configure Luna Studio’s dataset-import or evaluator-registration backend.

​
Update, rotate, or remove credentials

  • Update or remove an in-app record — changes the personal or workspace record represented by the Splunk Agent Observability card. Under the current limitation, this does not change the credentials used by dataset import or registration.
  • Rotate the effective key — have the deployment operator replace the configured API key and restart or roll out the affected backend workload as required by your deployment.
  • Disable the effective connection — clearing the deployment settings disables future Splunk Agent Observability imports and registrations.
Removing the Splunk Agent Observability connection does not unregister any evaluators already published to the Splunk Agent Observability evaluators store. Those evaluators remain live until you remove them from the Splunk Agent Observability platform itself.

​
Where to go next