Please note: PEM 7.3 is scheduled for release in June of 2018; until version 7.3 is available, the PEM server and agent distributed with the Ark console will not be functional. At the time of the Ark 3.0 release, PEM configuration information is displayed in the Ark console, but is still pending full implementation.Postgres Enterprise Manager (PEM) is an enterprise management tool designed to assist database administrators, system architects, and performance analysts in administering, monitoring, and tuning PostgreSQL and EnterpriseDB Advanced Server database servers. PEM can manage and monitor a handful of servers or hundreds of servers from a single console, allowing complete control over all aspects of your databases.A PEM installation consists of a PEM server, one or more PEM agents, and the backing database server (named pem). The PEM server includes a web interface that allows you to monitor and manage the database instances that are registered with a PEM agent. A PEM agent is responsible for returning metric information to the PEM server, and performing tasks on the database instances that are registered with that agent.The Ark 3.0 console includes a pre-configured PEM server, a PEM agent, and the pem backing database.During deployment, you will be prompted to use the PEM Server Mode drop-down listbox to select a deployment mode:
• Select DISABLE to indicate that clusters deployed on the host should not be registered with the PEM server.
• Select LOCAL to indicate that you would like to use the PEM server that resides on your local host. If you select LOCAL, the PEM deployment will use default values assigned by the installer.
o The PEM Server Port will monitor port 5432.
• Select REMOTE to indicate that you would like to use a PEM server that resides on another host, and provide connection information on the Ark console deployment dialog (see Figure 2.8).
o Provide the IP address of the PEM server host in the PEM Server IP Address field.
o Specify the port monitored for connections by the PEM server in the PEM Server Port field.
o Provide the name that should be used when authenticating with the PEM server in the PEM Server Username field.
o Provide the password associated with the PEM server user in the PEM Server Password field.If you select REMOTE, whenever a new cluster node is created on this console, it will be registered for monitoring by the PEM server.https://address_of_Ark_console/pemWhen you've authenticated with the server, the PEM web interface allows you to manage your monitored nodes (see Figure 2.10).PEM documentation is available via the PEM web interface Help menu, or at the EnterpriseDB website at:If your Ark clusters are provisioned with private IP addresses, they may not be reachable from the PEM server. If this is the case, you will not be able to use the PEM Dashboard to remotely browse the database server. PEM agents running on the Ark cluster nodes will be able to report status to the PEM Server.For example, replica nodes created on OpenStack are not assigned public floating IP addresses, so you can't browse them remotely from the PEM Dashboard by default. You must manually assign a public IP address before being able to browse each node.This feature is implemented before the release of PEM 7.3; until PEM 7.3 is released, the default behavior of Ark is to simply skip installation of the edb-pem-agent rpm and registration of the agent and database servers. When PEM 7.3 is available, Ark 3.0 will automatically install the agent and register cluster nodes with the server. Any currently running nodes will not automatically be updated to register with PEM. To monitor an existing node, you will be required to manually register the node with the PEM server.