Restez organisé à l'aide des collections
Enregistrez et classez les contenus selon vos préférences.
Fleet Engine propose un service de journalisation de base pour ses requêtes d'API et ses charges utiles de réponse. Vous pouvez utiliser ces journaux pour analyser, surveiller et déboguer vos applications. Pour en savoir plus sur Fleet Engine, consultez Qu'est-ce que le service Fleet Engine ?.
Fleet Engine envoie des journaux spécifiques au service à Cloud Logging. Vous pouvez ainsi utiliser l'explorateur de journaux de la console Google Cloud, l'API Cloud Logging ou des commandes en ligne pour y accéder et les analyser.
La liste suivante décrit ces aspects clés de Cloud Logging.
Cloud Logging est un service géré qui vous permet de stocker, de rechercher, d'analyser et de surveiller les données et les événements de journalisation de Google Cloud et d'autres sources, et d'envoyer des alertes le cas échéant. Pour en savoir plus, consultez la documentation Cloud Logging et les journaux de la plate-forme Cloud dans la documentation Cloud.
L'explorateur de journaux est un outil de la console Google Cloud qui vous permet de récupérer, d'afficher et d'analyser les entrées de journal. Pour en savoir plus, consultez Afficher les journaux à l'aide de l'explorateur de journaux.
L'API Cloud Logging vous permet d'effectuer des tâches liées à la journalisation de manière programmatique, y compris lire et écrire des entrées de journal, et créer des métriques basées sur les journaux. Pour en savoir plus, consultez la présentation de l'API Cloud Logging.
Sauf indication contraire, le contenu de cette page est régi par une licence Creative Commons Attribution 4.0, et les échantillons de code sont régis par une licence Apache 2.0. Pour en savoir plus, consultez les Règles du site Google Developers. Java est une marque déposée d'Oracle et/ou de ses sociétés affiliées.
Dernière mise à jour le 2025/08/29 (UTC).
[null,null,["Dernière mise à jour le 2025/08/29 (UTC)."],[[["\u003cp\u003eFleet Engine automatically logs API requests, responses, and errors, including those from the Driver SDK, to Cloud Logging for analysis and debugging.\u003c/p\u003e\n"],["\u003cp\u003eYou can access and analyze Fleet Engine logs using the Google Cloud Console Logs Explorer, the Cloud Logging API, or the Google Cloud CLI.\u003c/p\u003e\n"],["\u003cp\u003eCloud Logging offers features for storing, searching, analyzing, monitoring, and alerting on log data, providing insights into your Fleet Engine application's activity.\u003c/p\u003e\n"],["\u003cp\u003eComprehensive 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.\u003c/p\u003e\n"]]],["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"],null,["# Cloud Logging\n\nFleet Engine offers a basic logging service for its API requests and\nresponse payloads. You can use these logs to analyze, monitor, and debug your\napplications. For details about Fleet Engine, see [What is the Fleet\nEngine service?](/maps/documentation/mobility/fleet-engine/essentials).\n\nFleet Engine sends service-specific logs to Cloud Logging, so\nthat you can use the Google Cloud console Logs Explorer, the\nCloud Logging API, or command-line commands to access and analyze them.\nThe following list describes these key aspects of Cloud Logging.\n\n- **Cloud Logging** is a managed service that lets you store, search,\n analyze, monitor, and alert on logging data and events from Google Cloud and\n other sources. For more information, see the [Cloud Logging\n documentation](https://cloud.google.com/logging/docs) and [Cloud platform logs](https://cloud.google.com/logging/docs/api/platform-logs) in\n the Cloud documentation.\n\n- **Logs Explorer** is a tool of the Google Cloud console that\n lets you retrieve, view, and analyze log entries. For details, see [View\n logs by using the Logs Explorer](https://cloud.google.com/logging/docs/view/logs-explorer-interface).\n\n- The **Cloud Logging API** lets you programmatically accomplish\n logging-related tasks, including reading and writing log entries and\n creating log-based metrics. To learn more, see [Cloud Logging API\n overview](https://cloud.google.com/logging/docs/reference/api-overview).\n\n- The **Google Cloud CLI** has a group of commands that provide a command-line\n interface to the Cloud Logging API. For details, see [Google Cloud\n Command Line Interface](https://cloud.google.com/cli) and [gcloud logging](https://cloud.google.com/sdk/gcloud/reference/logging)\n\n| **Note:** Cloud Logging has usage and retention limits. To understand how to manage your logging costs and avoid unexpected charges, see [Google Cloud\n| Observability pricing](https://cloud.google.com/stackdriver/pricing#logging-costs).\n\nFleet Engine logs\n-----------------\n\nFleet Engine sends the following information to\nCloud Logging:\n\n- All Authenticated REST and gRPC requests and responses.\n\n- Error responses.\n\n- Requests, responses, and error messages from calls initiated to\n Fleet Engine by the [Driver SDK](/maps/documentation/mobility/driver-sdk).\n\nFor a list of all available log messages and schema, see the [Fleet Engine API\nLogging Integration Reference for on-demand trips](/maps/documentation/mobility/operations/cloud-logging/reference/tasks/rest) and the [Fleet Engine API\nLogging Integration Reference for scheduled tasks](/maps/documentation/mobility/operations/cloud-logging/reference/trips/rest).\n\nWhat's next\n-----------\n\nTo get started with Cloud Logging, see [Set up\nCloud Logging](/maps/documentation/mobility/operations/cloud-logging/setup)."]]
