[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-05 (世界標準時間)。"],[],[],null,["# Signal capture overview\n\nThis document offers information about telemetry signals such as metrics, logs,\ntraces, and statistics that are captured for Spanner.\n\nSpanner generates observability data, including\nmetrics, logs, traces, and statistics. You can set up capturing for some\nsignals that are not captured. You can use these signals to get a\ncomplete picture of how your system is performing.\n\nSpanner metrics\n---------------\n\nMetrics are numeric data about database health or performance, such as request\nlatency or CPU utilization, that you measure at regular intervals over time.\n\n[Cloud Monitoring](/monitoring/docs/monitoring-overview) regularly\nmeasures your service and usage of the Google Cloud resources.\nTo view all the server-side and client-side metrics collected by\nSpanner, see [Metrics list](/spanner/docs/metrics).\n\nIf you need custom client-side metrics beyond the metrics collected by\nSpanner, you can set up custom client-side metrics\nusing [OpenTelemetry](/spanner/docs/capture-custom-metrics-opentelemetry)\nor [OpenCensus](/spanner/docs/capture-custom-metrics-opencensus).\n| **Note:** [OpenCensus is deprecated](https://opentelemetry.io/blog/2023/sunsetting-opencensus/). We recommend using OpenTelemetry to capture the custom client-side metrics.\n\nCustom client-side metrics can incur charges through your observability backend.\n\nFor example, if you use Cloud Monitoring as your backend, you are billed\naccording to\n[Cloud Monitoring pricing](/stackdriver/pricing#monitoring-pricing-summary).\n\n\nSpanner logs\n------------\n\nA log is a generated record of system activity over time. Each log is\na collection of time-stamped log entries, and each log entry describes an\nevent at a specific point in time. For more information about enabling logs,\nsee [Enable Data Access audit logs](/logging/docs/audit/configure-data-access).\n[Cloud Logging](/logging/docs/overview) collects logging data from\ncommon application components. For a list of log types collected by\nSpanner,\nsee [Spanner audit logs](/spanner/docs/audit-logging).\n\nSpanner traces\n--------------\n\nTraces represent the path of a request through your application.\nTraces let you follow the flow of a request and help you\nto identify the root cause of an issue.\nYou can configure Spanner client libraries\nto export client-side and server-side traces using OpenTelemetry APIs.\nFor more information about trace collection using OpenTelemetry,\nsee [Trace collection overview](/spanner/docs/tracing-overview).\n\nSpanner statistics tables\n-------------------------\n\nSpanner offers a set of built-in statistic tables that you can\nquery to gain more information about the following:\n\n- Queries\n- Reads\n- Transactions\n- Locks\n- Table sizes\n- Table operations\n\nFor more information about the available tables, see\n[Spanner built-in statistics tables overview](/spanner/docs/introspection).\n\nWhat's next\n-----------\n\n- [Spanner metrics list](/spanner/docs/metrics)\n- [Client-side metrics overview](/spanner/docs/view-manage-client-side-metrics)\n- [Capture custom client-side metrics using OpenTelemetry](/spanner/docs/capture-custom-metrics-opentelemetry)\n- [Set up trace collection using OpenTelemetry](/spanner/set-up-tracing)\n- [Spanner built-in statistics tables overview](/spanner/docs/introspection)\n- [OpenTelemetry documentation](https://opentelemetry.io/docs/what-is-opentelemetry/)"]]
