Database identifier

Each database instance monitored with Datadog has a unique identifier. For Postgres, MySQL, SQL Server and Oracle this identifier can be configured using the database_identifier.template path in the integration configuration. Most users can leave this option as the default; it is primarily useful when multiple database instances are hosted on one machine.

| Note that each instance will be billed as a host for Database Monitoring.

Reported hostname

The reported_hostname configuration allows users to override the automatic resolution of host for a single database instance. This is useful when connecting to a database through a proxy, or when host resolution produces a different name than the one associated with the Datadog infrastructure host.

Examples

Multiple Postgres instances each on different port:

database_identifier:
  template: $resolved_hostname:$port

SQL Server host with multiple instances:

database_identifier:
  template: $resolved_hostname:$instance_name

MySQL instance with the same hostname running in multiple environments:

database_identifier:
  template: $env-$resolved_hostname

Connecting to an Oracle database with multiple CDBs through a proxy:

reported_hostname: my-oracle.mydomain.com
database_identifier:
  template: $resolved_hostname\$cdb_name