Skip to content

Commit 6d1c924

Browse files
authored
Merge pull request #6095 from EnterpriseDB/release-2024-09-25a
Release 2024-09-25a
2 parents ad5dbff + 5e64931 commit 6d1c924

File tree

26 files changed

+1012
-950
lines changed

26 files changed

+1012
-950
lines changed

advocacy_docs/community/contributing/styleguide.mdx

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,7 @@ Included in this guide:
7474
* 13 [Dates](#dates)
7575
* 14 [Terminology considerations](#terminology-considerations)
7676
* 15 [Trademark symbols](#trademark-symbols)
77+
* 16 [Frontmatter](#frontmatter)
7778

7879
## Language and tone
7980

@@ -656,4 +657,20 @@ Examples: EDB Postgres® AI, EDB Postgres® Analytics, EDB Postgres® Machine Le
656657
657658
For other trademarks, the documentation site already includes a general disclaimer at the footer of every page called "Trademark" which links to https://www.enterprisedb.com/trademarks.
658659
Contrary to the specifications on [Trademarks](https://www.enterprisedb.com/trademarks), don't include the symbol in page titles,
659-
because the symbol can affect how search engines index and find pages.
660+
because the symbol can affect how search engines index and find pages.
661+
662+
## Frontmatter
663+
664+
The frontmatter is located at the top of every Markdown page and allows you to specify metadata and options in YAML language. Frontmatter lets you control how a page renders.
665+
666+
Ensure your page, at minimum, includes a `title` and `description` as metadata. It can include other metadata such as `navTitle`, `deepToC`, and so on.
667+
668+
```yaml
669+
---
670+
title: Working with the repo
671+
description: Step-by-step instructions to install and use the docs repo.
672+
---
673+
```
674+
675+
!!!note
676+
Ensure the `description` has a final stop (period), even if it isn't a full grammatical sentence. Descriptions are used to dynamically build a summary for each section in `index` pages. Since all descriptions are then displayed next to each other, add a full stop to ensure visual consistency.

advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/monitoring_and_logging/monitoring_using_biganimal_observability/index.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Monitoring using BigAnimal Observability"
2+
title: "Monitoring using Cloud Service Observability"
33
redirects:
44
- /biganimal/latest/using_cluster/05_monitoring_and_logging/monitoring_using_pemx/
55

@@ -10,6 +10,7 @@ Cloud Service Observability is an integrated monitoring and alerting solution in
1010
Cloud Service Observability renders insightful charts that empower you to actively monitor each metric's behavior. It provides a streamlined path for you to take prompt and informed actions based on the generated alerts. This cohesive monitoring and alert system ensures comprehensive oversight and prompt responses in the Cloud Service environment.
1111

1212
When you log in, Cloud Service Observability monitoring widgets are displayed on the overview page on the project summary page. These widgets are available only for the deployed Postgres clusters and aren't available for the clusters in the provisioning process. They provide high-level, key information on:
13+
1314
- Memory
1415
- CPU
1516
- Storage usage percentages

advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx

Lines changed: 20 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -130,26 +130,27 @@ Here is an example `beacon_agent.yaml` file configured for a database named `sal
130130

131131
```yaml
132132
agent:
133-
access_key: $BEACON_AGENT_ACCESS_KEY
134-
access_key_grpc_header: "x-access-key"
135-
batch_size: 100
136-
beacon_server: "beacon.biganimal.com:443"
137-
feature_flag_interval: 10m0s
138-
project_id: "<project ID>"
139-
providers:
140-
- "onprem"
133+
access_key: "$BEACON_AGENT_ACCESS_KEY"
134+
access_key_grpc_header: "x-access-key"
135+
batch:
136+
size: 100
137+
beacon_server: "beacon.biganimal.com:443"
138+
feature_flag_interval: 10m0s
139+
project_id: "<project ID>"
140+
providers:
141+
- "onprem"
141142
provider:
142-
onprem:
143-
databases:
144-
sales_reporting:
145-
dsn: $DSN
146-
tags:
147-
- "sales"
148-
- "reports"
149-
host:
150-
resource_id: "postgresql.lan"
151-
tags: []
152-
poll_interval: 5m0s
143+
onprem:
144+
databases:
145+
sales_reporting:
146+
dsn: "$DSN"
147+
tags:
148+
- "sales"
149+
- "reports"
150+
host:
151+
resource_id: "postgresql.lan"
152+
tags: []
153+
poll_interval: 5m0s
153154
```
154155

155156
## Test Beacon Agent locally.

product_docs/docs/jdbc_connector/42.7.3.1/02_requirements_overview.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ This table lists the latest JDBC Connector versions and their supported correspo
1919

2020
| JDBC Connector | EPAS16 | EPAS 15 | EPAS 14 | EPAS 13 | EPAS 12 | EPAS 11 |
2121
| ---------------------------------------------------------- | --------|-------- | ------- | ------- | ------- | ------- |
22+
| [42.7.3.1](01_jdbc_rel_notes/jdbc_42.7.3.1_rel_notes) | Y | Y | Y | Y | Y | N |
2223
| [42.5.4.2](01_jdbc_rel_notes/jdbc_42.5.4.2_rel_notes) | Y | Y | Y | Y | Y | Y |
2324
| [42.5.4.1](01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes) | N | Y | Y | Y | Y | Y |
2425
| [42.5.1.2](01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes) | N | Y | Y | Y | Y | Y |

0 commit comments

Comments
 (0)