This dashboard offers a clear view into Google ADK usage and performance. It highlights key metrics such as token consumption, model distribution, error rates, request volumes, latency trends, and agent usage. Teams can also track which services and languages are leveraging Google ADK along with detailed records of errors, to better understand adoption patterns and optimize reliability and efficiency.
To start sending Google ADK telemetry to SigNoz, follow the Google ADK monitoring guide.
Tokens are the foundation of Google ADK. By splitting input tokens (user prompts) and output tokens (model responses), this panel shows exactly how much work the system is doing. Over time, you can monitor efficiency, spot growth in adoption, and balance consumption across workloads.
This line shows the total tokenm usage over time per service.
Not every request makes it through successfully. This panel tracks the percentage of Google ADK calls that return errors. It’s a quick way to identify reliability issues and ensure your applications maintain a smooth, dependable experience.
Google ADK offers multiple model variants, each optimized for different tasks. This panel reveals which models are being called most often helping you track preferences, measure adoption of newer releases, and align usage with performance or cost goals.
This breakdown reveals how token usage is spread across different model variants, helping you identify which models drive the most consumption and optimize your workload distribution for cost and performance.
This pie chart shows the distribution of total calls made by agent, to highlight which agents are being used the most by users.
This chart captures the volume of requests sent to Google ADK over time, letting you see demand patterns, identify high-traffic windows, and plan infrastructure or cost controls accordingly.
How fast does Google ADK respond under load? This panel measures the 95th percentile duration of requests over time, surfacing potential slowdowns, spikes, or regressions. By keeping an eye on responsiveness, teams can ensure a consistent developer and user experience.
Google ADK powers a variety of applications across different services and programming languages. This breakdown shows where the API is being adopted—making it easier to understand usage patterns across your stack and identify opportunities for optimization.
The Logs panel lists all Google ADK service related logs. Teams can use this for deep troubleshooting, auditing usage patterns, and correlating issues with specific request flows. Clicking on a row links back to the corresponding log entry for full traceability. This Errors panel logs all recorded errors and when clicking on an individual record, you are sent to the trace where the error originated.