Skip to main content

Server Environments

PMP4PG supports two environment types that allow you to distinguish production servers from non-production servers across your fleet.

Environment Types​

EnvironmentLabelPurpose
RUNProductionLive production PostgreSQL instances
BUILDNon-ProductionDevelopment, staging, QA, testing instances

The environment is set in the agent's config.yml at registration time:

server:
  environment: RUN    # or BUILD
note

The environment cannot be changed after registration without re-registering the agent. Choose carefully at registration time.

How Environments Are Used​

Global Dashboard Filtering​

The Global Dashboard displays all servers regardless of environment by default. You can filter the servers grid to show only RUN or BUILD servers using the environment filter.

{screenshot: dashboard-environment-filter}

Visual Distinction​

Each server in the dashboard and server list displays a color-coded environment badge:

  • 🟢 RUN — production servers
  • 🔵 BUILD — non-production servers

{screenshot: server-environment-badges}

Operational Context​

The environment label helps DBAs and DevOps engineers quickly distinguish between critical production instances and non-production environments when reviewing alerts, metrics or AWR reports.

Setting the Environment​

The environment is configured in the agent's config.yml before registration:

server:
  hostname: "pg-staging-01"
  environment: BUILD         # Non-production
  datacenter: "eu-west-1"

For a production server:

server:
  hostname: "pg-prod-01"
  environment: RUN           # Production
  datacenter: "eu-west-1"

Next Steps​