Skip to content

Commit 2afb730

Browse files
authored
Merge branch 'develop' into aidb-6.2.0
2 parents c5360b9 + 839c443 commit 2afb730

File tree

4 files changed

+15
-13
lines changed

4 files changed

+15
-13
lines changed

advocacy_docs/tools/agent/usage_reporting/index.mdx

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
11
---
2-
title: Usage reporting
2+
title: Enabling usage reporting
33
navTitle: Usage reporting
4-
description: Learn about usage reporting with the Agent.
4+
description: Enable usage reporting with the EDB Postgres AI agent.
55

66
---
77

8-
The Agent can provide valuable usage data, helping EDB understand how customers are using our products and facilitating core-based licensing and entitlements. This functionality is available regardless of whether you're using Hybrid Manager (HM) for monitoring or are running an on-premises database server.
8+
The EDB Postgres AI agent can provide valuable usage data, helping EDB understand how customers are using our products and facilitating core-based licensing and entitlements. This functionality is available regardless of whether you're using Hybrid Manager (HM) for monitoring or are running an on-premises database server.
99

10-
Usage reporting with the Agent is an opt-in service. Data is only sent to EDB when you explicitly enable it. When enabled, the agent sends a new report every 12 hours by default, starting with the first time the agent runs.
10+
Usage reporting with the EDB Postgres AI agent is an opt-in service, so it is not enabled by default. Data is only sent to EDB when you explicitly enable it. When enabled, the EDB Postgres AI agent sends a new report every 12 hours by default, starting with the first time the EDB Postgres AI agent runs.
1111

1212
## What type of data is collected?
1313

14-
When configured to send usage data, the Agent generates a small report containing environment metadata and resource usage. This includes information like:
14+
When configured to send usage data, the EDB Postgres AI agent generates a small report containing environment metadata and resource usage. This includes information like:
1515

1616
- Operating system details
1717
- Memory and CPU usage
@@ -25,13 +25,15 @@ When configured to send usage data, the Agent generates a small report containin
2525

2626
When configured, reporting data goes to `https://pg-usage.enterprisedb.com`, an EDB-managed S3 bucket.
2727

28-
## How do I enable usage reporting with the Agent?
28+
## How do I enable usage reporting with the EDB Postgres AI agent?
2929

30-
If you are using the Hybrid Manager for centralized observability and monitoring, you can enable reporting as part of your Agent's configuration. See [Enabling usage reporting in HM](/edb-postgres-ai/latest/hybrid-manager/using_hybrid_manager/monitoring/mon_ext_dbs/mon_with_agent/configure_agent/usage_reporting/).
30+
If you are using the Hybrid Manager for centralized observability and monitoring, you can enable reporting as part of your EDB Postgres AI agent's configuration. See [Enabling usage reporting in HM](/edb-postgres-ai/latest/hybrid-manager/using_hybrid_manager/monitoring/mon_ext_dbs/mon_with_agent/configure_agent/usage_reporting/).
3131

3232
If you have a standalone deployment of a database server (PostgreSQL, EPAS, PGE), and you don't wish to use the Hybrid Manager, see [Enabling usage reporting for standalone databases](/tools/agent/stand_alone/).
3333

34-
## How many Agents do I need to track several databases?
34+
If you are operating in an air-gapped environment, you can create an usage report as a JSON file within the EDB Postgres AI agent's configuration page and upload it through the option **PGAI Agent Reporting** under the **Tools** section in the left side pane of the [EDB Customer Portal](https://techsupport.enterprisedb.com).
35+
36+
## How many EDB Postgres AI agents do I need to track several databases?
3537

3638
Regardless of your setup, EDB recommends deploying one Agent per host machine with self-managed database clusters. While a single Agent can track databases across different hosts, keeping the Agent on the same machine is necessary to capture full host-level metrics.
3739

product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/10_printing_pdn_node_db_id.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ title: "Printing the primary definition node database ID (printpdndbid)"
88

99
## Synopsis
1010

11-
`-printmdnbid -repsvrfile pubsvrfile`
11+
`-printmdndbid -repsvrfile pubsvrfile`
1212

1313
## Parameters
1414

product_docs/docs/pgd/6.2/overview/quickstart/first-cluster.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ To create your first PGD cluster, you can use the Docker Compose file provided b
2929
3. Run the following command to download the PGD Docker Compose file:
3030

3131
```bash
32-
curl -L https://enterprisedb.com/docs/pgd/latest/quickstart/assets/pgd_quickstart.sh | bash
32+
curl -L https://enterprisedb.com/docs/pgd/overview/latest/quickstart/assets/pgd_quickstart.sh | bash
3333
```
3434

3535
This will download the PGD Docker Quickstart kit, which includes the Docker Compose file and other necessary files to get started with PGD Essential.

product_docs/docs/postgres_for_kubernetes/1/security.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -62,8 +62,8 @@ please use this medium to report it.
6262
Operator images for {{name.ln}} are built and [published](./private_edb_registries.mdx) as part of our release process.
6363
See [Release Notes](rel_notes/) for information on the latest available operator versions.
6464

65-
Operand images are build and published weekly for each supported PostgreSQL version
66-
(including [EDB Postgres Extended](/pge/latest/) and [EDB Postgres Advanced](/epas/latest/)).
65+
Operand images are built and published monthly for each supported PostgreSQL version
66+
(including [EDB Postgres Extended](/pge/latest/) and [EDB Postgres Advanced](/epas/latest/)).
6767

6868
Images undergo scanning with the following tools:
6969

@@ -73,7 +73,7 @@ Images undergo scanning with the following tools:
7373
components, validates license consistency.
7474

7575
!!! Important
76-
All operand images are automatically rebuilt weekly by our pipelines to incorporate security updates at the base image and package level, providing **patch-level updates** for the container images distributed to EDB download sites.
76+
All operand images are automatically rebuilt monthly by our pipelines to incorporate the latest security updates at both the base image and package levels, providing **patch-level updates** for the container images distributed to EDB download sites.
7777
!!!
7878

7979
!!! Warning

0 commit comments

Comments
 (0)