概要

AlloyDB は、要求の厳しいトランザクションワークロードに対応した、PostgreSQL 互換のフルマネージド型データベースです。 オープンソースの PostgreSQL と 100% の互換性を保ちながら、エンタープライズクラスの性能と可用性を提供します。

Google AlloyDB からメトリクスを取得して、以下のことができます。

  • AlloyDB クラスターのパフォーマンスを視覚化する。
  • AlloyDB インスタンスのパフォーマンスとデータベースを関連付ける。

セットアップ

インストール

Google Cloud Platform インテグレーションをまだセットアップしていない場合は、最初にセットアップします。これ以外に必要なインストール手順はありません。

収集データ

Google AlloyDB logs are collected with Google Cloud Logging and sent to a Dataflow job through a Cloud Pub/Sub topic. If you haven’t already, set up logging with the Datadog Dataflow template.

Once this is done, export your Google AlloyDB logs from Google Cloud Logging to the Pub/Sub topic:

  1. Google Cloud Logging のページに移動し、Google AlloyDB のログを絞り込みます。
  2. Create Export をクリックし、シンクに名前を付けます。
  3. 宛先として “Cloud Pub/Sub” を選択し、その目的で作成された Pub/Sub トピックを選択します。: Pub/Sub トピックは別のプロジェクトに配置できます。
  4. 作成をクリックし、確認メッセージが表示されるまで待ちます。

収集データ

メトリクス

gcp.alloydb.database.postgresql.insights.cluster.storgae.usage
(gauge)
The total AlloyDB storage in bytes across the entire cluster.
Shown as byte
gcp.alloydb.database.postgresql.insights.aggregate.execution_time
(count)
Accumulated query execution time since the last sample. This is the sum of CPU time, IO wait time, lock wait time, process context switch, and scheduling for all the processes involved in the query execution.
Shown as microsecond
gcp.alloydb.database.postgresql.insights.aggregate.io_time
(count)
Accumulated IO time since the last sample.
Shown as microsecond
gcp.alloydb.database.postgresql.insights.aggregate.latencies
(count)
Query latency distribution.
Shown as microsecond
gcp.alloydb.database.postgresql.insights.aggregate.lock_time
(count)
Accumulated lock wait time since the last sample.
Shown as microsecond
gcp.alloydb.database.postgresql.insights.aggregate.row_count
(count)
The number of retrieved or affected rows since the last sample.
gcp.alloydb.database.postgresql.insights.aggregate.shared_blk_access_count
(count)
Shared blocks (regular tables and indexed) accessed by statement execution.
gcp.alloydb.database.postgresql.insights.perquery.execution_time
(count)
Accumulated execution times per user per database per query. This is the sum of CPU time, IO wait time, lock wait time, process context switch, and scheduling for all the processes involved in the query execution.
Shown as microsecond
gcp.alloydb.database.postgresql.insights.perquery.io_time
(count)
Accumulated IO time since the last sample.
Shown as microsecond
gcp.alloydb.database.postgresql.insights.perquery.latencies
(count)
Query latency distribution.
Shown as microsecond
gcp.alloydb.database.postgresql.insights.perquery.lock_time
(count)
Accumulated lock wait time since the last sample.
Shown as microsecond
gcp.alloydb.database.postgresql.insights.perquery.row_count
(count)
The number of retrieved or affected rows since the last sample.
gcp.alloydb.database.postgresql.insights.perquery.shared_blk_access_count
(count)
Shared blocks (regular tables and indexed) accessed by statement execution.
gcp.alloydb.database.postgresql.insights.pertag.execution_time
(count)
Accumulated execution times since the last sample. This is the sum of CPU time, IO wait time, lock wait time, process context switch, and scheduling for all the processes involved in the query execution.
Shown as microsecond
gcp.alloydb.database.postgresql.insights.pertag.io_time
(count)
Accumulated IO time since the last sample.
Shown as microsecond
gcp.alloydb.database.postgresql.insights.pertag.latencies
(count)
Query latency distribution.
Shown as microsecond
gcp.alloydb.database.postgresql.insights.pertag.lock_time
(count)
Accumulated lock wait time since the last sample.
Shown as microsecond
gcp.alloydb.database.postgresql.insights.pertag.row_count
(count)
The number of retrieved or affected rows since the last sample.
gcp.alloydb.database.postgresql.insights.pertag.shared_blk_access_count
(count)
Shared blocks (regular tables and indexed) accessed by statement execution.
gcp.alloydb.instance.cpu.average_utilization
(gauge)
Mean CPU utilization across all currently serving nodes of the instance from 0 to 100.
gcp.alloydb.instance.cpu.maximum_utilization
(gauge)
Maximum CPU utilization across all currently serving nodes of the instance from 0 to 100.
gcp.alloydb.instance.cpu.vcpus
(gauge)
The number of vCPUs allocated to each node in the instance.
gcp.alloydb.instance.memory.min_available_memory
(gauge)
The minimum available memory across all currently serving nodes of the instance. The available memory is an estimate of memory in bytes available for allocation on the VM including memory that is currently used, but can be potentially freed.
Shown as byte
gcp.alloydb.instance.postgres.abort_count
(count)
The number of transactions that were rolled back across all serving nodes of the instance.
gcp.alloydb.instance.postgres.average_connections
(gauge)
The mean number of active and idle connections to AlloyDB across serving nodes of the instance.
gcp.alloydb.instance.postgres.commit_count
(count)
The number of committed transactions across all serving nodes of the instance.
gcp.alloydb.instance.postgres.connections_limit
(gauge)
The current limit on the number of connections per node of the AlloyDB instance.
gcp.alloydb.instance.postgres.instances
(gauge)
The number of nodes in the instance, along with their status, which can be either up or down.
gcp.alloydb.instance.postgres.replication.maximum_lag
(gauge)
The maximum replication time lag calculated across all serving read replicas of the instance. The replication time lag is derived from the replay_lag value.
Shown as millisecond
gcp.alloydb.instance.postgres.replication.replicas
(gauge)
The number of read replicas connected to the primary instance.
gcp.alloydb.instance.postgres.total_connections
(gauge)
The number of active and idle connections to the AlloyDB instance across serving nodes of the instance.
gcp.alloydb.instance.postgres.transaction_count
(count)
The number of committed and rolled back transactions across all serving nodes of the instance.

イベント

Google AlloyDB インテグレーションには、イベントは含まれません。

サービスチェック

Google AlloyDB インテグレーションには、サービスのチェック機能は含まれません。

トラブルシューティング

ご不明な点は、Datadog のサポートチームまでお問い合わせください。

PREVIEWING: mervebolat/span-id-preprocessing