Cloud Logging
Stay organized with collections
Save and categorize content based on your preferences.
Fleet Engine offers a basic logging service for its API requests and
response payloads. You can use these logs to analyze, monitor, and debug your
applications. For details about Fleet Engine, see What is the Fleet
Engine service?.
Fleet Engine sends service-specific logs to Cloud Logging, so
that you can use the Google Cloud console Logs Explorer, the
Cloud Logging API, or command-line commands to access and analyze them.
The following list describes these key aspects of Cloud Logging.
Cloud Logging is a managed service that lets you store, search,
analyze, monitor, and alert on logging data and events from Google Cloud and
other sources. For more information, see the Cloud Logging
documentation and Cloud platform logs in
the Cloud documentation.
Logs Explorer is a tool of the Google Cloud console that
lets you retrieve, view, and analyze log entries. For details, see View
logs by using the Logs Explorer.
The Cloud Logging API lets you programmatically accomplish
logging-related tasks, including reading and writing log entries and
creating log-based metrics. To learn more, see Cloud Logging API
overview.
The Google Cloud CLI has a group of commands that provide a command-line
interface to the Cloud Logging API. For details, see Google Cloud
Command Line Interface and gcloud logging
Fleet Engine logs
Fleet Engine sends the following information to
Cloud Logging:
All Authenticated REST and gRPC requests and responses.
Error responses.
Requests, responses, and error messages from calls initiated to
Fleet Engine by the Driver SDK.
For a list of all available log messages and schema, see the Fleet Engine API
Logging Integration Reference for on-demand trips and the Fleet Engine API
Logging Integration Reference for scheduled tasks.
What's next
To get started with Cloud Logging, see Set up
Cloud Logging.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-03-11 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-11 UTC."],[[["Fleet Engine automatically logs API requests, responses, and errors, including those from the Driver SDK, to Cloud Logging for analysis and debugging."],["You can access and analyze Fleet Engine logs using the Google Cloud Console Logs Explorer, the Cloud Logging API, or the Google Cloud CLI."],["Cloud Logging offers features for storing, searching, analyzing, monitoring, and alerting on log data, providing insights into your Fleet Engine application's activity."],["Comprehensive logging details, including available log messages and schema, can be found in the Fleet Engine API Logging Integration Reference for on-demand and scheduled tasks."]]],["Fleet Engine provides logs of API requests and responses to Cloud Logging for analysis, monitoring, and debugging. Cloud Logging offers storage, search, analysis, and monitoring of log data via the Logs Explorer, Cloud Logging API, or Google Cloud CLI. Fleet Engine logs include authenticated REST/gRPC requests/responses, error responses, and Driver SDK interactions. Cloud Logging has usage limits and costs. For more information about log messages and schema, see the specific Fleet Engine API Logging Integration Reference pages. To begin, configure Cloud Logging.\n"]]
