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.