[null,null,["อัปเดตล่าสุด 2025-08-31 UTC"],[[["\u003cp\u003eLog-based metrics are created using filters to count matching log entries within a project, like tracking trip creation events.\u003c/p\u003e\n"],["\u003cp\u003eMetrics data starts accumulating only after metric creation and doesn't include pre-existing log entries.\u003c/p\u003e\n"],["\u003cp\u003eYou can set up alerts to get notified when a metric violates pre-defined thresholds.\u003c/p\u003e\n"],["\u003cp\u003eFor further log analysis and insights, you can integrate with BigQuery.\u003c/p\u003e\n"]]],["Log-based metrics track log entries matching a filter within a project. An example is tracking the number of trips created over time using a specific query. Metrics are populated only with data from logs received after the metric's creation. Users can set up alerts for metrics that exceed defined thresholds, with notifications sent to specified channels. Further, logs can be analysed using BigQuery.\n"],null,["Log-based metrics count the log entries that match a given filter for the\ncurrent project. For example, you could create a metric to track the number of\ntrips created over time with the following query: \n\n resource.type=\"audited_resource\"\n resource.labels.method=\"maps.fleetengine.v1.TripService.ReportBillableTrip\"\n\nFor an overview and instructions on how to create log-based metrics, see\n[Log-based metrics](https://cloud.google.com/logging/docs/logs-based-metrics).\n| **Note:** The data for a user-defined log-based metric comes only from log entries received after the metric is created. A metric isn't retroactively populated with data from previously logged entries.\n\nSet up alerts\n\nYou can create alerts to notify customers when a metric falls out of a defined\nthreshold, and specify notification channels for those alerts. See [Configure\nlog-based alerting policies](https://cloud.google.com/logging/docs/alerting/log-based-alerts).\n\nWhat's next\n\nLearn how to [analyse logs with BigQuery](/maps/documentation/mobility/operations/cloud-logging/big-query)."]]
