Merge pull request #1843 from EnterpriseDB/release/2021-09-14

Release: 2021-09-14
EnterpriseDB · Sep 14, 2021 · 5ead131 · 5ead131
2 parents 0308fc8 + a4b5dd4
commit 5ead131
Show file tree

Hide file tree

Showing 454 changed files with 2,454 additions and 2,230 deletions.
diff --git a/advocacy_docs/kubernetes/cloud_native_postgresql/architecture.mdx b/advocacy_docs/kubernetes/cloud_native_postgresql/architecture.mdx
@@ -156,9 +156,9 @@ instance acting as a primary at all times. This means that applications can
 only write inside a single Kubernetes cluster, at any time.
 
 !!! Tip
-   If you are interested in a PostgreSQL architecture where all instances accept writes, 
-   please take a look at  [BDR (Bi-Directional Replication) by EDB](https://www.enterprisedb.com/docs/bdr/latest/). 
-   For Kubernetes, BDR will have its own Operator, expected late in 2021. 
+    If you are interested in a PostgreSQL architecture where all instances accept writes, 
+    please take a look at  [BDR (Bi-Directional Replication) by EDB](https://www.enterprisedb.com/docs/bdr/latest/). 
+    For Kubernetes, BDR will have its own Operator, expected late in 2021. 
 
 However, for business continuity objectives it is fundamental to:
 

diff --git a/product_docs/convert_pem_online_help.sh b/product_docs/convert_pem_online_help.sh
@@ -4,12 +4,21 @@ cd "${0%/*}"
 
 ./convert.sh
 
-rsync -a --delete content_build/pem/ docs/pem/8.1.0/pem_online_help/
+rm content_build/pem/release_notes*.mdx
+rm content_build/pem/pem_release_notes*.mdx
 
-rm docs/pem/8.1.0/pem_online_help/release_notes*.mdx
+# eliminate absolute paths
+grep -rli '<img' * | xargs -i@ sed -i 's/<img src="\/..\/images\//<img src="..\/images\//' @
+# eliminate figures
+grep -rli '<img' * | xargs -i@ sed -i -E 's/<figure><img src="([^"]+)" class="align-center" alt="([^"]+)" \/><figcaption aria-hidden="true"><em>[^<]+<\/em><\/figcaption><\/figure>/!\[\2](\1)/' @
+# eliminate HTML images
+grep -rli '<img' * | xargs -i@ sed -i -E 's/<img src="([^"]+)" class="align-center" alt="([^"]+)" \/>/!\[\2](\1)/' @
+
+rsync -a --delete content_build/pem/ docs/pem/8/pem_online_help/
 
 cd ..
 
-node scripts/normalize/titleRefs.js "product_docs/docs/pem/8.1.0/pem_online_help/**/*.mdx"
-node scripts/normalize/slashEscapedLessThan.js "product_docs/docs/pem/8.1.0/pem_online_help/**/*.mdx"
-node scripts/normalize/markdown.js "product_docs/docs/**/*.mdx" "product_docs/docs/pem/8.1.0/**/*.mdx"
+node scripts/normalize/titleRefs.js "product_docs/docs/pem/8/pem_online_help/**/*.mdx"
+node scripts/normalize/slashEscapedLessThan.js "product_docs/docs/pem/8/pem_online_help/**/*.mdx"
+node scripts/normalize/markdown.js "product_docs/docs/**/*.mdx" "product_docs/docs/pem/8/**/*.mdx"
+python scripts/legacy_redirects/add_legacy_redirects.py
diff --git a/product_docs/docs/pem/7/pem_rel_notes/05_712_rel_notes.mdx b/product_docs/docs/pem/7/pem_rel_notes/05_712_rel_notes.mdx
diff --git a/product_docs/docs/pem/8/images/alert_template_export.png b/product_docs/docs/pem/8/images/alert_template_export.png
diff --git a/product_docs/docs/pem/8/images/alert_template_import.png b/product_docs/docs/pem/8/images/alert_template_import.png
diff --git a/product_docs/docs/pem/8/images/alert_template_import_browse.png b/product_docs/docs/pem/8/images/alert_template_import_browse.png
diff --git a/product_docs/docs/pem/8/images/alert_template_import_successful.png b/product_docs/docs/pem/8/images/alert_template_import_successful.png
diff --git a/product_docs/docs/pem/8/images/alert_template_skip_both.png b/product_docs/docs/pem/8/images/alert_template_skip_both.png
diff --git a/product_docs/docs/pem/8/images/alert_template_skip_dependent_probe.png b/product_docs/docs/pem/8/images/alert_template_skip_dependent_probe.png
diff --git a/product_docs/docs/pem/8/images/alert_templates_tab.png b/product_docs/docs/pem/8/images/alert_templates_tab.png
diff --git a/product_docs/docs/pem/8/images/create_server_pem_agent_advanced_tab.png b/product_docs/docs/pem/8/images/create_server_pem_agent_advanced_tab.png
diff --git a/product_docs/docs/pem/8/images/create_server_pem_agent_tab.png b/product_docs/docs/pem/8/images/create_server_pem_agent_tab.png
diff --git a/product_docs/docs/pem/8/images/custom_probes.png b/product_docs/docs/pem/8/images/custom_probes.png
diff --git a/product_docs/docs/pem/8/images/custom_probes_alt_code.png b/product_docs/docs/pem/8/images/custom_probes_alt_code.png
diff --git a/product_docs/docs/pem/8/images/custom_probes_code.png b/product_docs/docs/pem/8/images/custom_probes_code.png
diff --git a/product_docs/docs/pem/8/images/custom_probes_columns.png b/product_docs/docs/pem/8/images/custom_probes_columns.png
diff --git a/product_docs/docs/pem/8/images/custom_probes_export.png b/product_docs/docs/pem/8/images/custom_probes_export.png
diff --git a/product_docs/docs/pem/8/images/custom_probes_general.png b/product_docs/docs/pem/8/images/custom_probes_general.png
diff --git a/product_docs/docs/pem/8/images/custom_probes_import.png b/product_docs/docs/pem/8/images/custom_probes_import.png
diff --git a/product_docs/docs/pem/8/images/custom_probes_import_browse.png b/product_docs/docs/pem/8/images/custom_probes_import_browse.png
diff --git a/product_docs/docs/pem/8/images/custom_probes_import_error.png b/product_docs/docs/pem/8/images/custom_probes_import_error.png
diff --git a/product_docs/docs/pem/8/images/custom_probes_import_skip_msg.png b/product_docs/docs/pem/8/images/custom_probes_import_skip_msg.png
diff --git a/product_docs/docs/pem/8/images/custom_probes_import_successful.png b/product_docs/docs/pem/8/images/custom_probes_import_successful.png
diff --git a/product_docs/docs/pem/8/images/pem_alert_templates_pre-def.png b/product_docs/docs/pem/8/images/pem_alert_templates_pre-def.png
diff --git a/product_docs/docs/pem/8/images/pem_alert_templates_tab.png b/product_docs/docs/pem/8/images/pem_alert_templates_tab.png
diff --git a/product_docs/docs/pem/8/index.mdx b/product_docs/docs/pem/8/index.mdx
@@ -14,6 +14,7 @@ navigation:
   - pem_agent
   - pem_bart
   - pem_ent_feat
+  - pem_ha_setup
   - pem_security_best_practices
   - pem_sqlprofiler
   - "#Online Help"

diff --git a/product_docs/docs/pem/8/pem_admin/02_registering_server.mdx b/product_docs/docs/pem/8/pem_admin/02_registering_server.mdx
@@ -106,6 +106,8 @@ Use fields on the `Advanced` tab to specify details that are used to manage the
 
 Use fields on the `PEM Agent` tab to specify connection details for the PEM agent:
 
+On `Connection Parameters` tab
+
 -   Move the `Remote monitoring?` slider to `Yes` to indicate that the PEM agent does not reside on the same host as the monitored server. When remote monitoring is enabled, agent level statistics for the monitored server will not be available for custom charts and dashboards, and the remote server will not be accessible by some PEM utilities (such as Audit Manager, Capacity Manager, Log Manager, Postgres Expert and Tuning Wizard).
 
 -   Use the drop-down listbox to the right of the `Bound agent` label to select a PEM agent . One agent can monitor multiple Postgres servers.  
@@ -131,14 +133,23 @@ For more information about using SSL encryption, see the [PostgreSQL documentati
 
 -   Specify the name of the role that agent should use when connecting to the server in the `User name` field. Note that if the specified role is not a database superuser, then some of the features will not work as expected. For the list of features that do not work if the specified role is not a database superuser, see [Agent privileges](../pem_agent/03_managing_pem_agent/#managing_pem_agent). If you are using Kerberos Authentication method then specify the user having `bdr_monitor` or `bdr_superuser` role in this field.
 
-If you are using Postgres version 10 or above, you can use the `pg_monitor` role to grant the required privileges to a non-superuser. For information about `pg_monitor` role, see [Default Roles](https://www.postgresql.org/docs/current/default-roles.html).
+    If you are using Postgres version 10 or above, you can use the `pg_monitor` role to grant the required privileges to a non-superuser. For information about `pg_monitor` role, see [Default Roles](https://www.postgresql.org/docs/current/default-roles.html).
 
 -   Specify the name of the user that agent should use when connecting to the server in the `User name` field. Note that if the specified user is not a database superuser, then some of the features will not work as expected. If you are using Postgres version 10 or above, you can use the `pg_monitor` role to grant the required privileges to a non-superuser. For information about `pg_monitor` role, see [Default Roles](https://www.postgresql.org/docs/current/default-roles.html).
 
 -   Specify the password that the agent should use when connecting to the server in the `Password` field, and verify it by typing it again in the `Confirm password` field. If you do not specify a password, you will need to configure the authentication for the agent manually; for example, you can use a `.pgpass` file, and it must be present and accessible on the system, where agent is installed.
 
+![The PEM Agent Advanced tab of the Create – Server dialog](../images/create_server_pem_agent_advanced_tab.png)
+
+On the `Advanced` tab
+
 -   Set the `Allow takeover?` slider to `Yes` to specify that the server may be taken over by another agent. This feature allows an agent to take responsibility for the monitoring of the database server if, for example, the server has been moved to another host as part of a high availability failover process.
 
+-   Use the `+` sign to add the database you want to exclude from the PEM Monitoring. You cannot exclude the database mentioned on the `Connection Parameters` tab of the `PEM Agent` tab.
+
+!!! Note
+    The database-level probes do not execute for excluded databases, but the server-level probes may collect the database statistics.
+
 ![The Create Server dialog (BART - General tab)](../images/create_server_bart_general.png)
 
 Use the fields on the `General` tab under `BART` tab to describe the general properties of the BART Server that will map to the PEM server:

diff --git a/product_docs/docs/pem/8/pem_ent_feat/04_pem_erd_tool.mdx b/product_docs/docs/pem/8/pem_ent_feat/04_pem_erd_tool.mdx
@@ -1,6 +1,7 @@
 ---
 title: "The ERD Tool"
 ---
+
 !!! tip "New Feature "
     The ERD Tool is available in PEM 8.1.0 and later.