Skip to content

Latest commit

 

History

History
113 lines (86 loc) · 4.96 KB

File metadata and controls

113 lines (86 loc) · 4.96 KB

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

Breaking Changes

  • Local configuration directory renamed from ~/.galileo to ~/.splunk. The override environment variable is now SPLUNK_AO_HOME_DIR (previously GALILEO_HOME_DIR).

Fixed

  • Agent and workflow output conversion now removes confirmed repeated input history and keeps only the last message as the terminal output; intermediate tool-call and tool-response messages are no longer included in gen_ai.output.messages for full-history spans. The trim is now gated on the prefix-match dedup check so parallel tool-call outputs (e.g. a ToolNode with multiple simultaneous calls) are never collapsed to one message when the output does not echo the input.
  • gen_ai.output.messages assistant entries whose parts contain a tool_call but carry no explicit finish_reason now receive "tool_call" instead of "unknown". Explicit source finish reasons and tool-response messages are unaffected.

0.2.1 - 2026-08-07

Fixed

  • Galileo multimodal URL and base64 data blocks now export as OpenTelemetry GenAI uri and blob message parts for both input and output messages while preserving modality, MIME type, and supported extension fields.

0.2.0 - 2026-08-06

Fixed

  • Agent Control spans exported over OTLP now include the control discriminator and complete agent_control.* field set required for backend classification and Controls-card rendering.

Changed

  • Config file renamed (HYBIM-918): The non-secret debug snapshot written to ~/.galileo/ on logout/reset is now named splunk-ao-config.json (was galileo-python-config.json). The old file can be deleted or ignored — it is never read back and has no effect on authentication or config resolution.
  • Evaluator terminology alignment in docs and errors: Updated SplunkAOEvaluators docstrings, agent stream/evaluator API docstrings, and user-visible error messages to use evaluator and agent stream vocabulary following the SplunkAOMetricsSplunkAOEvaluators rename. Enum values are documented as matching scorer labels via the legacy /scorers API paths. The public metrics= parameter name is unchanged for API compatibility. Renamed stale test_galileo_metrics_* and test_lookup_by_galileo_metrics_enum test identifiers.

0.1.1 - 2026-08-03

Removed

  • Breaking: monitor_progress() job_id parameter removed (HYBIM-931). The deprecated job_id keyword argument of Experiment.monitor_progress() has been fully removed. Callers passing job_id= must remove that argument.

0.1.0 - 2026-07-31

Added

  • Added deployment-aware configuration and authentication for Splunk Observability Cloud and standalone Agent Observability deployments.
  • Added O11y Cloud configuration through SPLUNK_AO_REALM, SPLUNK_AO_O11Y_TOKEN, and the optional SPLUNK_AO_O11Y_API_TOKEN.
  • Added native OTLP trace export for SDK handlers and standard OpenTelemetry or OpenInference instrumentations.
  • Added Project and Agent Stream routing by name or ID in both OTLP request headers and OpenTelemetry Resource attributes.
  • Added standard OpenTelemetry Resource detection, including a valid service.name fallback and support for OTEL_SERVICE_NAME.
  • Added structured input and output capture for workflow, agent, LLM, tool, and retriever spans, including supported multimodal content.

Changed

  • Completed spans are queued immediately in an OpenTelemetry BatchSpanProcessor and exported on its configured schedule.
  • flush() and async_flush() now drain completed spans without concluding an active operation.
  • Independent top-level decorated calls own separate traces, while nested calls remain children of their outer operation.
  • Exceptions from decorated functions, synchronous generators, and asynchronous generators are re-raised after telemetry finalization.
  • Reserved Agent Observability routing keys in OTEL_RESOURCE_ATTRIBUTES are removed so SDK routing configuration remains consistent with request headers.

Diagnostics

  • Standard OpenTelemetry exporter logging reports transport, authentication, retry, and non-2xx HTTP failures.
  • Successful HTTP responses that reject telemetry produce sanitized, rate-limited SDK error logs and a recovery log after a later accepted response.
  • Exporters expose bounded, read-only receiver-acknowledgement health. Health is unknown before an acknowledgement and after ordinary transport or non-2xx failures; it is not a delivery guarantee.