Conversation
The breaking changes in this range are narrow corrections and an upstream SDK requirement rather than a redesign, so this ships as a minor. Release-As: 2.9.0
Co-authored-by: George Weale <gweale@google.com> PiperOrigin-RevId: 979310995
…l execution Co-authored-by: George Weale <gweale@google.com> PiperOrigin-RevId: 979334063
…absolute Co-authored-by: George Weale <gweale@google.com> PiperOrigin-RevId: 979339666
Co-authored-by: adk-bot <223368873+adk-bot@users.noreply.github.com> Co-authored-by: GWeale <gweale@users.noreply.github.com>
Co-authored-by: George Weale <gweale@google.com> PiperOrigin-RevId: 979418259
Co-authored-by: George Weale <gweale@google.com> PiperOrigin-RevId: 980134869
Co-authored-by: adk-bot <223368873+adk-bot@users.noreply.github.com>
GCPBatchLogRecordProcessor cleared every record's `event_name`, so that Cloud Logging would name the log after `gcp.log_name` instead. Agent Engine needs that: all records have to land in the single `aiplatform.googleapis.com/reasoning_engine_stdout` log the stdout pipeline produced. Everywhere else it silently renamed the log. Off Agent Engine, CloudLoggingExporter derived the log id from the record's event name, so `gen_ai.client.inference.operation.details` records landed in a log of that name -- and anything named after the log id followed it, including a Cloud Logging to BigQuery sink writing a `gen_ai_client_inference_operation_details` table. Forcing the name to `adk-otel` left that table empty, and started an `adk_otel` table nothing queries. The event name is now cleared only on Agent Engine. `gcp.log_name` is still stamped everywhere, so records that carry no event name keep the default log name the old exporter gave them. Co-authored-by: Max Ind <maxind@google.com> PiperOrigin-RevId: 983826787
Co-authored-by: adk-bot <223368873+adk-bot@users.noreply.github.com>
Jacksunwei
added
the
ready to pull
Collaborator
|
Closed in favor of Piper CL 985397810 syncing version metadata and CHANGELOG directly. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Syncs version bump and CHANGELOG from release v2.9.2 to main.