Skip to content

Commit ae3b3ed

Browse files
mashhursrobbavey
andauthored
Remove tech preview from agent driven LS monitoring pages. (#17482)
* Remove tech preview from agent driven LS monitoring pages. Co-authored-by: Rob Bavey <[email protected]>
1 parent 3c6cbbf commit ae3b3ed

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

docs/reference/dashboard-monitoring-with-elastic-agent.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -85,8 +85,8 @@ Check out [Installing {{agent}}](docs-content://reference/fleet/install-elastic-
8585

8686
6. Configure the integration to collect metrics.
8787

88-
* Make sure that **Metrics (Technical Preview)** is turned on, and **Metrics (Stack Monitoring)** is turned off.
89-
* Under **Metrics (Technical Preview)**, make sure the {{ls}} URL setting points to your {{ls}} instance URLs.<br> By default, the integration collects {{ls}} monitoring metrics from `https://localhost:9600`. If that host and port number are not correct, update the `Logstash URL` setting. If you configured {{ls}} to use encrypted communications and/or a username and password, you must access it via HTTPS, and expand the **Advanced Settings** options, and fill in with the appropriate values for your {{ls}} instance.
88+
* Make sure that **Metrics (Elastic Agent)** is turned on (default), and **Metrics (Stack Monitoring)** is turned off.
89+
* Under **Metrics (Elastic Agent)**, make sure the {{ls}} URL setting points to your {{ls}} instance URLs.<br> By default, the integration collects {{ls}} monitoring metrics from `https://localhost:9600`. If that host and port number are not correct, update the `Logstash URL` setting. If you configured {{ls}} to use encrypted communications and/or a username and password, you must access it via HTTPS, and expand the **Advanced Settings** options, and fill in with the appropriate values for your {{ls}} instance.
9090

9191
7. Click **Save and continue**.<br> This step takes a minute or two to complete. When it’s done, you’ll have an agent policy that contains a system integration policy for the configuration you just specified.
9292
8. In the popup, click **Add {{agent}} to your hosts** to open the **Add agent** flyout.
@@ -129,7 +129,7 @@ It takes about a minute for {{agent}} to enroll in {{fleet}}, download the confi
129129

130130
After you have confirmed enrollment and data is coming in, click **View assets** to access dashboards related to the {{ls}} integration.
131131

132-
For traditional Stack Monitoring UI, the dashboards marked **[Logs {{ls}}]** are used to visualize the logs produced by your {{ls}} instances, with those marked **[Metrics {{ls}}]** for the technical preview metrics dashboards. These are populated with data only if you selected the **Metrics (Technical Preview)** checkbox.
132+
For traditional Stack Monitoring UI, the dashboards marked **[Logs {{ls}}]** are used to visualize the logs produced by your {{ls}} instances, with those marked **[Metrics {{ls}}]** for metrics dashboards. These are populated with data only if you selected the **Metrics (Elastic Agent)** checkbox.
133133

134134
:::{image} images/integration-assets-dashboards.png
135135
:alt: Integration assets

docs/reference/monitoring-with-elastic-agent.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ Check out [Installing {{agent}}](docs-content://reference/fleet/install-elastic-
9292

9393
6. Configure the integration to collect metrics
9494

95-
* Make sure that **Metrics (Stack Monitoring)** is turned on, and **Metrics (Technical Preview)** is turned off, if you want to collect metrics from your {{ls}} instance
95+
* Make sure that **Metrics (Stack Monitoring)** is turned on, and **Metrics (Elastic Agent)** is turned off, if you want to collect metrics from your {{ls}} instance.
9696
* Under **Metrics (Stack Monitoring)**, make sure the hosts setting points to your {{ls}} host URLs. By default, the integration collects {{ls}} monitoring metrics from `localhost:9600`. If that host and port number are not correct, update the `hosts` setting. If you configured {{ls}} to use encrypted communications, you must access it via HTTPS. For example, use a `hosts` setting like `https://localhost:9600`.
9797

9898
7. Choose where to add the integration policy.<br> Click **New hosts** to add it to new agent policy or **Existing hosts** to add it to an existing agent policy.
@@ -136,7 +136,7 @@ It takes about a minute for {{agent}} to enroll in {{fleet}}, download the confi
136136

137137
After you have confirmed enrollment and data is coming in, click **View assets** to access dashboards related to the {{ls}} integration.
138138

139-
For traditional Stack Monitoring UI, the dashboards marked **[Logs {{ls}}]** are used to visualize the logs produced by your {{ls}} instances, with those marked **[Metrics {{ls}}]** for the technical preview metrics dashboards. These are populated with data only if you selected the **Metrics (Technical Preview)** checkbox.
139+
For traditional Stack Monitoring UI, the dashboards marked **[Logs {{ls}}]** are used to visualize the logs produced by your {{ls}} instances, with those marked **[Metrics {{ls}}]** for metrics dashboards. These are populated with data only if you selected the **Metrics (Elastic Agent)** checkbox.
140140

141141
:::{image} images/integration-assets-dashboards.png
142142
:alt: Integration assets

docs/reference/serverless-monitoring-with-elastic-agent.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ For more info, check out the [Elastic Observability](docs-content://solutions/ob
4646
4747
**Configure the integration to collect metrics**
4848
49-
* Make sure that **Metrics (Stack Monitoring)** is OFF, and that **Metrics (Technical Preview)** is ON.
49+
* Make sure that **Metrics (Elastic Agent)** is turned on (default), and **Metrics (Stack Monitoring)** is turned off.
5050
* Set the {{ls}} URL to point to your {{ls}} instance.<br> By default, the integration collects {{ls}} monitoring metrics from `https://localhost:9600`. If that host and port number are not correct, update the `Logstash URL` setting. If you configured {{ls}} to use encrypted communications and/or a username and password, you must access it using HTTPS. Expand the **Advanced Settings** options, and fill in the appropriate values for your {{ls}} instance.
5151

5252

0 commit comments

Comments
 (0)