Google AlloyDB

개요

AlloyDB는 까다로운 트랜잭션 워크로드를 위한 완전 관리형 PostgreSQL 호환 데이터베이스입니다. 오픈 소스 PostgreSQL과 100% 호환성을 유지하면서 엔터프라이즈급 성능과 가용성을 제공합니다.

Google AlloyDB에서 메트릭을 가져와 다음을 수행할 수 있습니다.

  • AlloyDB 클러스터의 성능을 시각화합니다.
  • AlloyDB 인스턴스의 성능과 데이터베이스의 상관관계를 파악합니다.

설정

설치

아직 하지 않았다면, 먼저 Google Cloud Platform 통합을 설정하세요. 그 외 다른 설치 단계는 없습니다.

로그 수집

Google AlloyDB 로그는 Google Cloud Logging으로 수집되어 Cloud Pub/Sub 주제를 통해 Dataflow 작업으로 전송됩니다. 아직 설정하지 않았다면 Datadog Dataflow 템플릿을 사용하여 로깅을 설정하세요.

이 작업이 완료되면 Google AlloyDB 로그를 Google Cloud Logging에서 Pub/Sub 주제로 내보냅니다.

  1. Google Cloud Logging 페이지에서 Google AlloyDB 로그를 필터링합니다.
  2. Create Export를 클릭하고 싱크 이름을 지정하세요.
  3. “Cloud Pub/Sub"를 대상으로 선택하고 해당 목적으로 생성된 Pub/Sub 주제를 선택합니다. 참고: Pub/Sub 주제는 다른 프로젝트에 있을 수 있습니다.
  4. Create를 클릭하고 확인 메시지가 나타날 때까지 기다립니다.

수집한 데이터

메트릭

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: rtrieu/product-analytics-ui-changes