You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: advocacy_docs/tools/agent/usage_reporting/index.mdx
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,17 @@
1
1
---
2
-
title: Usage reporting
2
+
title: Enabling usage reporting
3
3
navTitle: Usage reporting
4
-
description: Learn about usage reporting with the Agent.
4
+
description: Enable usage reporting with the EDB Postgres AI agent.
5
5
6
6
---
7
7
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.
9
9
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.
11
11
12
12
## What type of data is collected?
13
13
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:
15
15
16
16
- Operating system details
17
17
- Memory and CPU usage
@@ -25,13 +25,15 @@ When configured to send usage data, the Agent generates a small report containin
25
25
26
26
When configured, reporting data goes to `https://pg-usage.enterprisedb.com`, an EDB-managed S3 bucket.
27
27
28
-
## How do I enable usage reporting with the Agent?
28
+
## How do I enable usage reporting with the EDB Postgres AI agent?
29
29
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/).
31
31
32
32
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/).
33
33
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?
35
37
36
38
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.
Copy file name to clipboardExpand all lines: product_docs/docs/postgres_for_kubernetes/1/security.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,8 +62,8 @@ please use this medium to report it.
62
62
Operator images for {{name.ln}} are built and [published](./private_edb_registries.mdx) as part of our release process.
63
63
See [Release Notes](rel_notes/) for information on the latest available operator versions.
64
64
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/)).
67
67
68
68
Images undergo scanning with the following tools:
69
69
@@ -73,7 +73,7 @@ Images undergo scanning with the following tools:
73
73
components, validates license consistency.
74
74
75
75
!!! 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.
0 commit comments