From f73198cfd898820e1a62f406d3f21f5f85072da1 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Tue, 3 Dec 2024 15:03:34 +0100 Subject: [PATCH 1/3] Typos in Install Beacon agent doc --- .../edb-postgres-ai/console/estate/agent/install-agent.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx index fa6d7c26ca0..c31dd14dbf8 100644 --- a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx +++ b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx @@ -82,7 +82,7 @@ export BEACON_AGENT_ACCESS_KEY= export BEACON_AGENT_PROJECT_ID= ``` -Running the `beacon-agent setup` command creates a configuration file in the Beacon configuration directory. using those environment variables. +Running the `beacon-agent setup` command creates a configuration file in the Beacon configuration directory using those environment variables. You also need to specify the Beacon configuration directory for storing the configuration file and the name of the configuration file to generate there. The `$HOME/.beacon/` file is one of the default locations which `beacon_agent` searches for `beacon_agent.yaml` when it starts. Using the `-file` flag tells the agent setup process to create its configuration file in a specific location. @@ -153,7 +153,7 @@ provider: poll_interval: 5m0s ``` -## Test Beacon Agent locally. +## Test Beacon Agent locally For an initial test of the agent, you can get it to send the data that it would normally send to the EDB Enterprise AI control plane to standard output, your terminal session, instead. This allows you to quickly confirm if the agent is successfully able to gather data and what that data looks like. From 633150cf87aa545ea5aa429a6d0e41a545b4a19b Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Tue, 3 Dec 2024 15:06:10 +0100 Subject: [PATCH 2/3] Removed heading 2 final stop --- .../edb-postgres-ai/console/estate/agent/install-agent.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx index c31dd14dbf8..7ca575059e7 100644 --- a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx +++ b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx @@ -210,7 +210,7 @@ agent: ``` -## Run Beacon Agent. +## Run Beacon Agent Run the agent using the following command: From 20c6766d2005b34a892b10842c2d1116eebc7a5d Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Wed, 4 Dec 2024 09:47:53 +0100 Subject: [PATCH 3/3] Committing DJs suggestion Co-authored-by: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> --- .../edb-postgres-ai/console/estate/agent/install-agent.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx index 7ca575059e7..6b9c1ecd041 100644 --- a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx +++ b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx @@ -82,7 +82,7 @@ export BEACON_AGENT_ACCESS_KEY= export BEACON_AGENT_PROJECT_ID= ``` -Running the `beacon-agent setup` command creates a configuration file in the Beacon configuration directory using those environment variables. +These environment variables are used when you run the `beacon-agent setup` command to create a configuration file in the Beacon configuration directory. You also need to specify the Beacon configuration directory for storing the configuration file and the name of the configuration file to generate there. The `$HOME/.beacon/` file is one of the default locations which `beacon_agent` searches for `beacon_agent.yaml` when it starts. Using the `-file` flag tells the agent setup process to create its configuration file in a specific location.