{"slug": "google-adk-observability-monitoring-with-opentelemetry", "title": "Google ADK Observability & Monitoring with OpenTelemetry", "summary": "Google has released a guide for setting up observability and monitoring for its Agent Development Kit (ADK) using OpenTelemetry, enabling developers to capture traces, logs, and metrics from AI agent applications. The integration with SigNoz provides unified dashboards and alerts to improve the reliability and responsiveness of AI agent workflows. The setup requires a SigNoz account, Python 3.10+, and a Google Gemini API key.", "body_md": "What is Google ADK Observability?\n\nGoogle ADK observability gives you full visibility into your AI agent applications by capturing traces, logs, and metrics with [OpenTelemetry](https://opentelemetry.io/). This guide walks you through setting up Google ADK monitoring and exporting all three signals to SigNoz.\n\nWith full Google ADK observability in SigNoz, you can correlate traces, logs, and metrics in unified dashboards, set alerts on latency and errors, and gain actionable insights to continuously improve the reliability and responsiveness of your AI agent workflows.\n\nPrerequisites\n\n- A\n[SigNoz Cloud account](https://signoz.io/teams/)with an active ingestion key or[Self Hosted SigNoz instance](https://signoz.io/docs/install/self-host/) - Internet access to send telemetry data to SigNoz Cloud\n- Python 3.10+ with\n`google-adk`\n\ninstalled - For Python:\n`pip`\n\ninstalled for managing Python packages - A Google Gemini API key. You can get it from\n[Google AI Studio platform](https://aistudio.google.com/app/api-keys)\n\nSet Up Google ADK Monitoring with OpenTelemetry\n\nFor more information on getting started with Google ADK in your Python environment, refer to the [Google ADK Python quickstart guide](https://google.github.io/adk-docs/get-started/python/).\n\nStep 1: Install dependencies\n\n```\npip install \\\n  opentelemetry-api \\\n  opentelemetry-sdk \\\n  opentelemetry-exporter-otlp \\\n  opentelemetry-instrumentation-httpx \\\n  opentelemetry-instrumentation-system-metrics \\\n  google-adk \\\n  openinference-instrumentation-google-adk\n```\n\nStep 2: Create an agent project\n\nRun the `adk create`\n\ncommand to start a new agent project.\n\n```\nadk create my_agent\n```\n\nStep 3: Update the .env file\n\nUpdate the `.env`\n\nfile in your generated module to include your generated Gemini API key:\n\n```\nGOOGLE_API_KEY=<YOUR_API_KEY>\n```\n\nStep 4: Import the necessary modules in your generated `agent.py`\n\n**Traces:**\n\n``` python\nfrom opentelemetry import trace\nfrom opentelemetry.sdk.resources import Resource\nfrom opentelemetry.sdk.trace import TracerProvider\nfrom opentelemetry.sdk.trace.export import BatchSpanProcessor\nfrom opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter\nfrom openinference.instrumentation.google_adk import GoogleADKInstrumentor\n```\n\n**Logs:**\n\n``` python\nfrom opentelemetry.sdk._logs import LoggerProvider, LoggingHandler\nfrom opentelemetry.sdk._logs.export import BatchLogRecordProcessor\nfrom opentelemetry.exporter.otlp.proto.http._log_exporter import OTLPLogExporter\nfrom opentelemetry._logs import set_logger_provider\nimport logging\n```\n\n**Metrics:**\n\n``` python\nfrom opentelemetry.sdk.metrics import MeterProvider\nfrom opentelemetry.exporter.otlp.proto.http.metric_exporter import OTLPMetricExporter\nfrom opentelemetry.sdk.metrics.export import PeriodicExportingMetricReader\nfrom opentelemetry import metrics\nfrom opentelemetry.instrumentation.system_metrics import SystemMetricsInstrumentor\nfrom opentelemetry.instrumentation.httpx import HTTPXClientInstrumentor\n```\n\nStep 5: Set up Traces\n\n``` python\nfrom opentelemetry.sdk.resources import Resource\nfrom opentelemetry.sdk.trace import TracerProvider\nfrom opentelemetry.sdk.trace.export import BatchSpanProcessor\nfrom opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter\nfrom opentelemetry import trace\nfrom openinference.instrumentation.google_adk import GoogleADKInstrumentor \nimport os\n\nresource = Resource.create({\"service.name\": \"<service_name>\"})\nprovider = TracerProvider(resource=resource)\nspan_exporter = OTLPSpanExporter(\n    endpoint= os.getenv(\"OTEL_EXPORTER_TRACES_ENDPOINT\"),\n    headers={\"signoz-ingestion-key\": os.getenv(\"SIGNOZ_INGESTION_KEY\")},\n)\nprocessor = BatchSpanProcessor(span_exporter)\nprovider.add_span_processor(processor)\ntrace.set_tracer_provider(provider)\n\nGoogleADKInstrumentor().instrument()\n```\n\nis the name of your service`<service_name>`\n\n→ SigNoz Cloud trace endpoint with appropriate`OTEL_EXPORTER_TRACES_ENDPOINT`\n\n[region](https://signoz.io/docs/ingestion/signoz-cloud/overview/#endpoint):`https://ingest.<region>.signoz.cloud:443/v1/traces`\n\n→ Your SigNoz`SIGNOZ_INGESTION_KEY`\n\n[ingestion key](https://signoz.io/docs/ingestion/signoz-cloud/keys/)\n\nUsing self-hosted SigNoz? Most steps are identical. To adapt this guide, update the endpoint and remove the ingestion key header as shown in [Cloud → Self-Hosted](https://signoz.io/docs/ingestion/cloud-vs-self-hosted#cloud-to-self-hosted).\n\nStep 6: Set up Metrics\n\n``` python\nfrom opentelemetry.sdk.resources import Resource\nfrom opentelemetry.sdk.metrics import MeterProvider\nfrom opentelemetry.exporter.otlp.proto.http.metric_exporter import OTLPMetricExporter\nfrom opentelemetry.sdk.metrics.export import PeriodicExportingMetricReader\nfrom opentelemetry import metrics\nfrom opentelemetry.instrumentation.system_metrics import SystemMetricsInstrumentor\nimport os\n\nresource = Resource.create({\"service.name\": \"<service_name>\"})\nmetric_exporter = OTLPMetricExporter(\n    endpoint= os.getenv(\"OTEL_EXPORTER_METRICS_ENDPOINT\"),\n    headers={\"signoz-ingestion-key\": os.getenv(\"SIGNOZ_INGESTION_KEY\")},\n)\nreader = PeriodicExportingMetricReader(metric_exporter)\nmetric_provider = MeterProvider(metric_readers=[reader], resource=resource)\nmetrics.set_meter_provider(metric_provider)\n\nmeter = metrics.get_meter(__name__)\n\n# turn on out-of-the-box metrics\nSystemMetricsInstrumentor().instrument()\nHTTPXClientInstrumentor().instrument()\n```\n\nis the name of your service`<service_name>`\n\n→ SigNoz Cloud endpoint with appropriate`OTEL_EXPORTER_METRICS_ENDPOINT`\n\n[region](https://signoz.io/docs/ingestion/signoz-cloud/overview/#endpoint):`https://ingest.<region>.signoz.cloud:443/v1/metrics`\n\n→ Your SigNoz`SIGNOZ_INGESTION_KEY`\n\n[ingestion key](https://signoz.io/docs/ingestion/signoz-cloud/keys/)\n\nUsing self-hosted SigNoz? Most steps are identical. To adapt this guide, update the endpoint and remove the ingestion key header as shown in [Cloud → Self-Hosted](https://signoz.io/docs/ingestion/cloud-vs-self-hosted#cloud-to-self-hosted).\n\nSystemMetricsInstrumentor provides system metrics (CPU, memory, etc.), and HTTPXClientInstrumentor provides outbound HTTP request metrics such as request duration. If you want to add custom metrics to your Google ADK application, see [Python Custom Metrics](https://signoz.io/opentelemetry/python-custom-metrics/).\n\nStep 7: Set up Logs\n\n``` python\nimport logging\nfrom opentelemetry.sdk.resources import Resource\nfrom opentelemetry._logs import set_logger_provider\nfrom opentelemetry.sdk._logs import LoggerProvider, LoggingHandler\nfrom opentelemetry.sdk._logs.export import BatchLogRecordProcessor\nfrom opentelemetry.exporter.otlp.proto.http._log_exporter import OTLPLogExporter\nimport os\n\nresource = Resource.create({\"service.name\": \"<service_name>\"})\nlogger_provider = LoggerProvider(resource=resource)\nset_logger_provider(logger_provider)\n\notlp_log_exporter = OTLPLogExporter(\n    endpoint= os.getenv(\"OTEL_EXPORTER_LOGS_ENDPOINT\"),\n    headers={\"signoz-ingestion-key\": os.getenv(\"SIGNOZ_INGESTION_KEY\")},\n)\nlogger_provider.add_log_record_processor(\n    BatchLogRecordProcessor(otlp_log_exporter)\n)\n# Attach OTel logging handler to root logger\nhandler = LoggingHandler(level=logging.INFO, logger_provider=logger_provider)\nlogging.basicConfig(level=logging.INFO, handlers=[handler])\n\nlogger = logging.getLogger(__name__)\n\n# Enable httpx logging to capture HTTP requests\nhttpx_logger = logging.getLogger(\"httpx\")\nhttpx_logger.setLevel(logging.DEBUG)\nhttpx_logger.addHandler(handler)\n```\n\nis the name of your service`<service_name>`\n\n→ SigNoz Cloud endpoint with appropriate`OTEL_EXPORTER_LOGS_ENDPOINT`\n\n[region](https://signoz.io/docs/ingestion/signoz-cloud/overview/#endpoint):`https://ingest.<region>.signoz.cloud:443/v1/logs`\n\n→ Your SigNoz`SIGNOZ_INGESTION_KEY`\n\n[ingestion key](https://signoz.io/docs/ingestion/signoz-cloud/keys/)\n\nUsing self-hosted SigNoz? Most steps are identical. To adapt this guide, update the endpoint and remove the ingestion key header as shown in [Cloud → Self-Hosted](https://signoz.io/docs/ingestion/cloud-vs-self-hosted#cloud-to-self-hosted).\n\nStep 8: Run your Google ADK Agent\n\nEnsure you have completed the steps above (traces, logs, and metrics configuration) before running your agent. All OpenTelemetry instrumentation must be initialized first.\n\nRun with command-line interface\n\nRun your agent using the `adk run`\n\ncommand-line tool.\n\n```\nadk run my_agent\n```\n\nRun with web interface\n\nThe ADK framework provides a web interface you can use to test and interact with your agent. You can start the web interface using the following command:\n\n```\nadk web --port 8000\n```\n\nView Google ADK Traces, Logs, and Metrics in SigNoz\n\nOnce configured, your Google ADK application automatically emits traces, logs, and metrics.\n\nGoogle ADK traces are available in SigNoz under the Traces tab:\n\nWhen you click on a trace in SigNoz, you'll see a detailed view of the trace, including all associated spans, along with their events and attributes.\n\nGoogle ADK logs are available in SigNoz under the Logs tab. You can also view correlated logs by clicking the \"Related Logs\" button in the trace view:\n\nWhen you click on any of these logs in SigNoz, you'll see a detailed view of the log, including attributes:\n\nGoogle ADK metrics are available in SigNoz under the Metrics tab:\n\nWhen you click on any of these metrics in SigNoz, you'll see a detailed view of the metric, including attributes:\n\nTroubleshooting Google ADK Observability\n\n[Troubleshooting Google ADK Observability](#troubleshooting-google-adk-observability)\n\nIf you don't see your telemetry data:\n\n**Verify network connectivity**- Ensure your application can reach SigNoz Cloud endpoints** Check ingestion key**- Verify your SigNoz ingestion key is correct** Wait for data**- OpenTelemetry batches data before sending, so wait 10-30 seconds after making API calls** Try a console exporter**— Enable a console exporter locally to confirm that your application is generating telemetry data before it’s sent to SigNoz\n\nGoogle ADK Dashboard\n\nYou can also import our prebuilt [Google ADK dashboard](https://signoz.io/docs/dashboards/dashboard-templates/google-adk-dashboard/), which provides specialized visualizations for monitoring your Google ADK usage in applications. The dashboard includes pre-built charts specifically tailored for LLM usage, along with import instructions to get started quickly.\n\nSetup OpenTelemetry Collector (Optional)\n\n[Setup OpenTelemetry Collector (Optional)](#setup-opentelemetry-collector-optional)\n\nWhat is the OpenTelemetry Collector?\n\nThink of the OTel Collector as a middleman between your app and SigNoz. Instead of your application sending data directly to SigNoz, it sends everything to the Collector first, which then forwards it along.\n\nWhy use it?\n\n**Cleaning up data**— Filter out noisy traces you don't care about, or remove sensitive info before it leaves your servers.** Keeping your app lightweight**— Let the Collector handle batching, retries, and compression instead of your application code.** Adding context automatically**— The Collector can tag your data with useful info like which Kubernetes pod or cloud region it came from.** Future flexibility**— Want to send data to multiple backends later? The Collector makes that easy without changing your app.\n\nSee [Switch from direct export to Collector](https://signoz.io/docs/opentelemetry-collection-agents/opentelemetry-collector/switch-to-collector/) for step-by-step instructions to convert your setup.\n\nFor more details, see [Why use the OpenTelemetry Collector?](https://signoz.io/docs/opentelemetry-collection-agents/opentelemetry-collector/why-to-use-collector/) and the [Collector configuration guide](https://signoz.io/docs/opentelemetry-collection-agents/opentelemetry-collector/configuration/).\n\nAdditional resources:\n\n- Set up\n[alerts](https://signoz.io/docs/product-features/alert-management)for high latency or error rates - Learn more about\n[querying traces](https://signoz.io/docs/product-features/trace-explorer) - Explore\n[log correlation](https://signoz.io/docs/product-features/logs-explorer)", "url": "https://wpnews.pro/news/google-adk-observability-monitoring-with-opentelemetry", "canonical_source": "https://signoz.io/docs/google-adk-observability", "published_at": "2026-06-01 00:00:00+00:00", "updated_at": "2026-06-04 12:55:50.919525+00:00", "lang": "en", "topics": ["ai-agents", "artificial-intelligence", "ai-tools", "ai-infrastructure", "mlops"], "entities": ["Google ADK", "SigNoz", "OpenTelemetry", "Google Gemini", "Google AI Studio", "Python"], "alternates": {"html": "https://wpnews.pro/news/google-adk-observability-monitoring-with-opentelemetry", "markdown": "https://wpnews.pro/news/google-adk-observability-monitoring-with-opentelemetry.md", "text": "https://wpnews.pro/news/google-adk-observability-monitoring-with-opentelemetry.txt", "jsonld": "https://wpnews.pro/news/google-adk-observability-monitoring-with-opentelemetry.jsonld"}}