* Upgrade Kotlin docs to adk-kotlin 0.9.0 and move off AdkWebServer
adk-kotlin 0.9.0 split the web server into AdkApiServer, which serves the agent
runtime contract headlessly, and AdkDevServer, which adds the development UI.
AdkWebServer is deprecated in that release and goes away at 1.0, so WebMain.kt
as written here stops compiling the day 1.0 ships.
The quickstart snippet now builds an AdkDevServer from an AdkServerConfig. That
drops three imports: AdkServerConfig.inMemory() supplies the agent loader and
the in-memory session and artifact services the old constructor took one by one.
Two behaviour notes come with the split. AdkWebServer pinned host to 0.0.0.0;
the new classes bind loopback, which is a visible change for anyone reaching the
server from a container or a remote box, so the page now says so and names the
host parameter in prose. It prints no worked example on purpose: the only value
such a snippet could carry is either 127.0.0.1, which overrides the default with
itself, or 0.0.0.0, which is a copyable way to publish an unauthenticated server
on every interface, and AdkDevServer construction is already shown in full
earlier on the page. And AdkApiServer is the headless half of the same config,
so it gets a short section rather than a bare mention - the bundled Kotlin API
reference is still generated at 0.5.0 and documents none of these classes, so a
link there would not have helped. The "not meant for production" warning now
sits directly after the screenshot, where go.md, java.md and python.md put it.
The dependency blocks readers copy from still pinned 0.8.0, and so did the
examples project. Verified on Maven Central that 0.9.0 is published for every
artifact named across these pages: -core, -processor, -webserver, -litertlm,
-a2a and -integrations. Checked the 0.9.0 POMs before bumping: Ktor still
resolves to 2.3.13 and a2a-java-sdk-client to 1.0.0.Final, so the explicit pins
stay correct and the two comments citing them only needed their version
reference moved. The `Kotlin v0.x` support badges are deliberately left alone:
they record the release a feature landed in, not the current version.
Verified by compiling: every snippet added here was compiled verbatim against
the published 0.9.0 artifacts on JDK 17, and the whole examples project still
builds at 0.9.0. As a negative control, the old snippet still compiles at 0.9.0
but emits the deprecation warning, which is what makes this a 1.0 break rather
than a present-day one. Note the Kotlin snippet check only builds .kt files
changed in the PR, so it will not cover a markdown-only change like this.
* Apply suggestion from @joefernandez
* Apply suggestion from @joefernandez
* Removing information bloat from the Get Started
see comments for where to locate this information
---------
Co-authored-by: Joe Fernandez <931947+joefernandez@users.noreply.github.com>
* Add the Kotlin tab for the BigQuery agent analytics quickstart
adk-kotlin 0.8.0 ships BigQueryAgentAnalyticsPlugin, so the quickstart's setup
group can carry a Kotlin tab alongside Python and Java. Transcluded, so CI
compiles and lints it.
The tab says plainly what the Kotlin plugin does not do, because a bare third
tab under this page's overview would promise far more than it delivers. It logs
INVOCATION_STARTING and INVOCATION_COMPLETED only - not the LLM, tool, state or
HITL events the page's table lists - fills the identity columns and content
while leaving trace_id, latency_ms and attributes null, and writes rows one at a
time through insertAll synchronously on the invocation path, not asynchronously
through the Storage Write API the page describes. Grounded in
BigQueryAgentAnalyticsPlugin.kt at the v0.8.0 tag, not the working tree.
Only the setup group gets Kotlin. The page's six other groups cover event
payloads and configuration surface the Kotlin plugin does not have.
The plugin lives in the integrations module, so examples/kotlin needs that
artifact to compile the snippet. One line is enough: unlike the a2a artifact,
google-adk-kotlin-integrations publishes google-cloud-bigquery and google-auth
on jvmApiElements, so the types its constructor defaults name are already on the
compile classpath.
Verified with the snippet ladder: L0 symbols, L1 compile, L2 ktlint, L3
transclusions, L5 registration and L6 badge all pass against the 0.8.0 pin.
* Scope the Kotlin BigQuery claims to what the plugin actually does
Review of the branch turned up five over-claims, all of the same kind: the page
describes the Python and Java plugins, and adding a Kotlin badge and tab quietly
extended every one of those promises to Kotlin.
- The page-level badge advertised Kotlin next to Python and Java on a page whose
opening promises Auto Schema Upgrade, tool provenance, HITL tracing, view
creation, ADK 2.0 workflow events and drop stats. Kotlin implements none of
them: BigQueryAgentAnalyticsPlugin overrides two Plugin callbacks. The
correction lived only inside the Kotlin tab, which a reader on the Python tab
never renders, so it moves to a page-level "Kotlin support" note next to the
pricing warning, following the "Java support" note this page already uses.
- The page says ingestion goes through the Storage Write API and links its
pricing. Kotlin calls tabledata.insertAll, a different billing line: charged
per inserted row with a 1 KB minimum and no monthly free tier, so cost tracks
invocation count, not bytes.
- BigQuerySchema creates no views, so the v_* names in the captured-events table
do not exist for Kotlin. A reader would have queried v_invocation_completed
and got a not-found.
- Configuration options is Python and Java only. Kotlin's whole surface is
BigQueryLoggerConfig's six fields, now listed, and `location` (default "US")
was undiscoverable - the snippet takes it as a parameter instead of pinning a
no-op tableName that already matches the default.
- Every logging failure is swallowed: a table that cannot be created or a row
that cannot be inserted is logged and the turn continues, so a misconfigured
agent looks healthy while writing nothing.
A second review pass caught a defect in the first pass's own fix: it told
readers to raise the log level for `bigquery_agent_analytics`, which is the
plugin's ADK name, not its logger. FloggerLoggingProvider names loggers with
kClass.java.name, so the text now gives the class name.
Verified: ./tools/kotlin-snippets/runner.sh build and lint both PASS on the
snippet (JDK 17), check_kotlin_snippets.sh passes, verify_snippets.py L0-L6 all
pass, and the page was rendered with the repo's own markdown extension set to
confirm the Kotlin tab joins the Python/Java tabbed set and the note renders as
an admonition rather than stray text.
* Update bigquery-agent-analytics.md
a few minor updates
* Update bigquery-agent-analytics.md
* Move the Kotlin scoping next to the content it scopes
The Kotlin support note described the page's tables as wrong from a
separate block, so a reader arriving at a table by anchor link, or
reading top to bottom, saw only the unqualified version. Each caveat now
sits with what it qualifies: the captured-events table says Kotlin logs
two event types and creates no views, the schema reference says which
columns are populated, and the lifecycle payload table records the
message content Kotlin writes.
Configuration options gains a Kotlin tab covering BigQueryLoggerConfig,
which is what the quickstart tab was asserting from the outside. With a
real section to point at, the quickstart can lead with how to use the
plugin rather than with what it cannot do.
Drop the BigQuery insert pricing detail; it belongs in the BigQuery
docs, not here.
* Update bigquery-agent-analytics.md
---------
Co-authored-by: Joe Fernandez <931947+joefernandez@users.noreply.github.com>
* Enhance BigQuery Agent Analytics documentation
Updated documentation to clarify Java and Python plugin differences, added details on dropped-event observability, and improved explanations of event types and attributes.
* Address review: use language support tags and a single drop-reasons table
- Replace the inline Java version callouts in prose with language-support-tag
blocks on the relevant sections (Built-in redaction, Dropped-event
observability; ADK 2.0 workflow events already carried one).
- Collapse the duplicated 'Drop reasons (Python)' / 'Drop reasons (Java)'
tables into a single table with a per-language column.
- Trim the duplicated Java scope prose in the intro and the ADK 2.0 note.
---------
Co-authored-by: Kristopher Overholt <koverholt@google.com>
Add a featured "Looker Block" subsection to "Build a dashboard" pointing to the
ready-to-use BigQuery Agent Analytics Looker Block on the Looker Marketplace,
and move the existing example-notebook guidance under a "Custom dashboard from a
notebook" subsection.
* Enhance BigQuery Agent Analytics with new options
Added options for OpenTelemetry correlation, custom metadata capture, and payload column projection in BigQuery Agent Analytics configuration.
* Fix formatting of Interactive Demo Notebook link
fix format
* docs(bigquery-agent-analytics): replace version callouts with language support tags
Address review feedback (koverholt) on PR #1942: the page used ad-hoc,
non-conventional version callouts (per-row table tags, footnotes, version
suffixes in headers, "post-vX.Y.Z" notes) that are unmaintainable and, in
places, stale.
- Drop the "(v2.4.0+)" / "(1.27.0+)" suffixes from config-table rows and
section headers; convey minimum versions with the repo-standard
language-support-tag blocks on the relevant sections instead
(Trace correlation → Python v2.4.0, Automatically Created Views →
Python v1.27.0, ADK 2.0 workflow events → Python v2.3.0).
- Remove the "‡ Added in v2.4.0" and "† ... not in v2.2.0" view-table
footnotes; the ADK 2.0 views/columns now point to the ADK 2.0 section.
- Remove the stale top "Version Requirement" note (v2.2.0 is no longer the
latest release; ADK 2.0 workflow support shipped in v2.3.0) and the stale
ADK 2.0 section note; de-version the intro prose.
- Remove the "Structured tool declarations (post-v2.4.0)" note: that shape is
not in any tagged release (v2.4.0 emits tools as a list of names); it will
be re-added under a language-support-tag once it ships.
- Trim the Trace-correlation section so it no longer restates the option table,
keeping only the cross-option constraints and the combined example.
* docs: update GOOGLE_GENAI_USE_VERTEXAI to GOOGLE_GENAI_USE_ENTERPRISE in configs and models
* docs: update GOOGLE_GENAI_USE_VERTEXAI in deployment and setup guides
* docs: update GOOGLE_GENAI_USE_VERTEXAI and Client parameter in integrations and streaming docs
* docs: update GOOGLE_GENAI_USE_VERTEXAI in tutorials and examples
---------
Co-authored-by: Joe Fernandez <931947+joefernandez@users.noreply.github.com>
* Enhance BigQuery Agent Analytics with reliability fixes
Added reliability and observability fixes for BigQuery Agent Analytics, including cross-region storage write routing, dropped-event tracking, and improved span management in Cloud Trace.
* Fix markdown formatting in BQAA doc
Resolve the code-fence/content-tab indentation issues flagged in review:
- Full example: restore the === "Python" content tab and indent the whole
Python code block uniformly to 8 spaces so it is a proper sibling of the
=== "Java" tab (previously the block was half-de-indented with an orphaned
opening fence next to a lone Java tab).
- Public methods: move the Python list inside the === "Python" tab (it had
been pasted at column 0, outside the tab) and remove the duplicated list
that ended up wrongly nested under the "Async context manager" bullet.
* Revise BigQuery Agent Analytics documentation
Updated version requirements and added details about ADK 2.0 multi-agent workflow features and event types. Enhanced descriptions for internal span tracking and storage behavior.
* Add context graph section to BigQuery Agent Analytics docs
Added a section on the context graph, detailing its purpose, structure, and operational references for materialization and deployment.
* Add files via upload
---------
Co-authored-by: Joe Fernandez <931947+joefernandez@users.noreply.github.com>
Updated the section on consuming logged data to clarify the use of the BigQuery Agent Analytics SDK and its example notebook for visualizing performance data.
Updated documentation for the BigQuery Agent Analytics plugin, removing outdated preview release information and adding links to the SDK and dashboard notebook.
Co-authored-by: Kristopher Overholt <koverholt@google.com>
* Enhance BigQueryAgentAnalyticsPlugin documentation
Updated documentation for BigQueryAgentAnalyticsPlugin configuration options, including new parameters for retry configuration and session metadata logging.
* Add view_prefix option to BigQuery Agent documentation
Updated documentation for BigQuery Agent Analytics plugin to include details about the new `view_prefix` configuration option and its impact on view naming conventions.
* Fix formatting and redaction notes in documentation
---------
Co-authored-by: Kristopher Overholt <koverholt@google.com>
* docs: home page
* updates based on feedback
* respond to review feedback
* docs: update gemini selector strings to "flash-latest"
* Update homepage.css
* Replace google.github.io/adk-docs URLs and /adk-docs/ paths with adk.dev
Migrate all hardcoded documentation references to use the new custom
domain. Update root-relative links to remove the /adk-docs/ subpath
prefix since the site will be served from the root of adk.dev.
* Additional fixes
* Revise title and description for root cause analysis
Updated section title for AI-Powered Root Cause Analysis and added description.
* Update section headers for advanced analysis queries
* Update bigquery-agent-analytics.md
removed numbers from heading to avoid confusion that these examples are meant to be executed in order
---------
Co-authored-by: Joe Fernandez <joefernandez@users.noreply.github.com>
Added details about the new feature for automatic view creation and updated the documentation to reflect changes in version 1.27.0.
Co-authored-by: Joe Fernandez <joefernandez@users.noreply.github.com>
* Update BigQuery Agent Analytics plugin documentation
Updated the documentation for the BigQuery Agent Analytics plugin to reflect changes in version requirements and features. Added details on new functionalities such as Auto Schema Upgrade, Tool Provenance tracking, and HITL Event Tracing.
* Update version requirement to Python 1.21.0
* Change default table name from agent_events_v2 to agent_events
---------
Co-authored-by: Joe Fernandez <joefernandez@users.noreply.github.com>
Updated OpenTelemetry initialization section and improved event type descriptions.
Co-authored-by: Joe Fernandez <joefernandez@users.noreply.github.com>
* docs: centralize 3P and 1P Integrations content
- move all content to integrations/
- frontmatter headings for all integration listings
* respond to review comments
Daria Wieliczko