Gemini Enterprise usage reporting is spread across several tools, not one universal report. Use app Analytics for adoption and engagement, Usage & Spending for quotas and recent usage costs, Cloud Monitoring for operational health, and Cloud Logging for audit history. The right setup depends on what you need to answer and which Gemini Enterprise edition your organization uses.
Choose the reporting surface that matches your question
| Question | Start here | Key limitation |
|---|---|---|
| Who is adopting or using the app? | App Analytics | Metrics refresh about every six hours; User Level requires allowlisting. Google Cloud Documentation |
| How much project usage or feature quota is consumed? | Gemini Enterprise > Usage & Spending > Usage | The view depends on edition and permissions; missing permissions can make values appear as zero or unknown. Google Cloud Documentation |
| Are requests and agents operating normally? | Cloud Monitoring Metrics Explorer | Agent metrics require instrumentation; app-scoped Engine metrics do not. Google Cloud Documentation |
| What user actions or content were logged? | Cloud Logging | Prompt and response content is sensitive and logged only when explicitly enabled. Google Cloud Documentation |
| What are the costs, including subscription SKUs? | Usage & Spending Billing tab for recent usage costs; Cloud Billing Reports for detail | The in-product Billing tab excludes license-based subscription costs. Google Cloud Documentation |
Set up app Analytics for adoption and engagement
Analytics reports adoption, usage and quality, agent activity, value, and user-level information. It is available only after a data store is connected to the app; metrics begin accruing from the time the data store is linked. Google Cloud Documentation says refreshes occur about every six hours, so the Analytics page may take several hours to become useful after app creation.
![The Google Gemini Bible: [3 in 1] The Most Updated Guide to Master Prompt Engineering, Automate Tasks, Create High-Quality Content, and Use AI for Business, Marketing, and 10x Productivity](https://m.media-amazon.com/images/I/51vX+osVJ4L._SL160_.jpg)
As an Amazon Associate I earn from qualifying purchases.
- In Google Cloud Console, open the Gemini Enterprise page and select your app.
- Select Analytics, choose the relevant tab—Adoption, Usage and Quality, Agent, Value, or User Level—and apply any available filters.
- Refresh the page to view updated metrics.
The User Level tab includes user identifiers and interactions and requires allowlisting. Search analytics have regional availability qualifications: they are in public preview for apps in US and EU multi-regions, and generally available for global apps. If the app has multiple connected data stores, Google recommends calling it through the engine resource to get results across the connected stores. Google Cloud Documentation: View and export analytics data
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Check feature usage and quotas
Usage & Spending shows different information depending on the subscription. Pay-as-you-go displays actual project usage. Standard, Plus, and Standard Emerging Market display pooled quotas; the documentation also identifies Frontline as an eligible active subscription for dashboard access.
- In Google Cloud Console, open Gemini Enterprise > Usage & Spending.
- Select the location of the licenses or subscription.
- Under Usage details, choose the subscription tier to inspect.
Permissions affect what the dashboard can show. The viewer needs monitoring.timeSeries.list to see quota usage; without it, usage can appear as zero. The serviceconsumermanagement.quota.get permission is needed to view quota limits; without it, a limit can appear as unknown. The Gemini Enterprise Administrator role (roles/discoveryengine.agentspaceAdmin) includes the first permission by default.
For license-based editions, quotas are pooled across project users. Except for storage and indexing, pooled quotas reset daily at midnight Pacific Time. AI developer tools instead use a seven-day cycle beginning with the first prompt or request. Pay-as-you-go consumption is not pooled by user license and requires an invoiced Cloud Billing account receiving an active monthly invoice. These schedules and eligibility details are product-specific and may change. Google Cloud Documentation
Configure Cloud Monitoring for operational health
Cloud Monitoring provides telemetry for requests and agents. App-scoped Engine metrics are collected without instrumentation; agent-scoped metrics require OpenTelemetry instrumentation. Metrics Explorer access requires Monitoring Viewer (roles/monitoring.viewer) and an existing app.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Enable instrumentation where needed
- Core Assistant: open the app’s Configurations > Observability settings.
- Supported Workflow Builder employee-made agents and Deep Research agents: open Agents, select the agent, then open Configuration.
Enable Instrumentation of OpenTelemetry traces and logs to access traces, spans, span logs, and associated agent metrics. Examples of app-scoped Engine metrics include request count—with API method, response code, query type, and model breakdowns—and end-to-end request latency. Agent metrics include sessions, conversational turns, tool invocation counts, and latency.
In Metrics Explorer, search for Gemini Enterprise metrics using the discoveryengine.googleapis.com/ prefix. Google Cloud Documentation places these metrics in the “all other Google Cloud metrics” tier, which has six-week default retention according to the cited documentation. Google Cloud Documentation
Set up Cloud Logging for audit history
Cloud Logging is for reviewing recorded activity, not a substitute for Analytics or Monitoring. Before configuring audit logs, enable observability, ensure an app exists, and have the Gemini Enterprise Admin role (roles/discoveryengine.agentspaceAdmin). To read logs, users need Logs Viewer (roles/logging.viewer).
- Enable observability for the app or agent as described above.
- In Google Cloud Console, open Logging > Logs Explorer and select the project where logging is enabled.
- Query Gemini Enterprise user activity and generative AI logs with this filter, replacing
PROJECT_IDwith your project ID:
logName="projects/PROJECT_ID/logs/discoveryengine.googleapis.com%2Fgemini_enterprise_user_activity" OR logName=~"projects/PROJECT_ID/logs/discoveryengine.googleapis.com%2Fgen_ai.*"Prompt and response content is included only if Enable logging of prompt inputs and response outputs is turned on. With that option off, text values are replaced with <elided> and other sensitive values are omitted. Enabling content logging first requires OpenTelemetry instrumentation and can capture personally identifiable information. Decide whether that content is necessary for your organization’s audit purpose, and restrict log access to authorized staff. Google Cloud Documentation
Review recent costs and detailed billing
The Billing tab under Gemini Enterprise > Usage & Spending summarizes overage and Pay-as-you-go usage costs across enabled features and tools for the last 30 days. It does not include license-based Gemini Enterprise subscription costs.
To see the Billing tab’s cost data, the user needs Gemini Enterprise Administrator on the project, Billing Account Viewer or Billing Account Administrator on the target billing account, and the relevant monitoring and quota permissions.
Quick Recap
Use Cloud Billing Reports for SKU detail
- Open the linked Cloud Billing account’s Reports page. Google’s documentation says Billing Reports require full billing-account permissions.
- For SKU-level detail, select the Gemini Enterprise costs by SKU preset, or filter for all Gemini Enterprise originating products and group by SKU. This separates subscription SKUs from overage SKUs.
- For a summary closer to the in-product Billing tab, filter for the same originating products, group by Originating Product, and select Charge period and Last 30 days.
Keep the reporting views distinct
- Use Analytics to understand user adoption and engagement.
- Use Usage & Spending to check edition-dependent quota consumption and recent usage costs.
- Use Monitoring to investigate request and agent performance.
- Use Logging to inspect recorded activity, with an explicit decision about sensitive prompt and response content.
- Use Cloud Billing Reports when you need subscription and overage costs broken down by SKU.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
