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
{{ message }}
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: src/tools/site-wide-analysis.md
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ The Site Wide Analysis Tool provides 24/7 real-time performance monitoring, repo
11
11
- Provides detailed information about your {{ site.data.var.ee }} installation
12
12
13
13
{:.bs-callout-info}
14
-
See the [user guide](https://docs.magento.com/user-guide/reports/site-wide-analysis-tool.html) for details about dashboards and reports.
14
+
See the [user guide](https://docs.magento.com/user-guide/reports/site-wide-analysis-tool.html) for details about enabling the Site Wide Analysis Tool and generating reports.
15
15
16
16
If you have an on-premises installation of {{ site.data.var.ee }}, you must install an agent on your infrastructure to use the tool.
17
17
@@ -23,7 +23,7 @@ If you have an on-premises installation of {{ site.data.var.ee }}, you must inst
23
23
24
24
The Site Wide Analysis Tool Agent allows you to use the Site Wide Analysis Tool for on-premises installations of {{ site.data.var.ee }}.
25
25
26
-
The agent collects application and business data, analyzes it, and provides additional insights about the health of your installation so that you can improve customer experience. It monitors your application and helps you identify performance, security, availability, and application issues.
26
+
The Site Wide Analysis Tool Agent collects application and business data, analyzes it, and provides additional insights about the health of your installation so that you can improve customer experience. It monitors your application and helps you identify performance, security, availability, and application issues.
27
27
28
28
Installing the agent requires the following steps:
29
29
@@ -43,7 +43,7 @@ Your on-premises infrastructure must meet the following requirements before inst
43
43
- Linux x86-64 distributions, such as RedHat Enterprise Linux (RHEL), CentOS, Ubuntu, Debian, and similar
44
44
45
45
{:.bs-callout-warning}
46
-
{{ site.data.var.ee }} is not supported on Microsoft Windows and macOS.
46
+
{{ site.data.var.ee }} is not supported on Microsoft Windows or macOS.
__If you have installed the extension__ and configured it using an existing API key for a different service, you must regenerate the API key and update it in the {{ site.data.var.ee }} Admin for the agent.
66
66
67
67
1. Put your website into [maintenance mode]({{ site.baseurl }}/guides/v2.4/install-gde/install/cli/install-cli-subcommands-maint.html).
68
-
1.Go to [accounts.magento.com](https://accounts.magento.com/).
68
+
1.Log in to [accounts.magento.com](https://accounts.magento.com/).
69
69
1. Click **API Portal**.
70
70
1. Click **Delete** next to the existing API key.
71
71
1.[Configure]({{ site.user_guide_url }}/system/saas.html) a new API key.
@@ -95,12 +95,12 @@ __If the extension is not installed__, use the following instructions to install
95
95
96
96
1.[Configure API keys]({{ site.user_guide_url }}/system/saas.html#createsaasenv) to connect the extension to your system.
97
97
98
-
### Install
98
+
### Install the agent
99
99
100
100
We have created a [shell script](https://github.com/magento-swat/install-agent-helpers/blob/main/install.sh) to simplify installation. We recommend using the shell script, but you can follow the [manual installation](#manual) method if necessary.
101
101
102
102
{:.bs-callout-info}
103
-
After the agent is installed, it will selfupdate when a new release is available.
103
+
After the agent is installed, it will self-update when a new release is available.
104
104
105
105
#### Scripted
106
106
@@ -229,7 +229,7 @@ We recommend configuring the agent to run as a service. If you have limited acce
229
229
230
230
#### Service
231
231
232
-
1. Copy the scheduler binary file to the directory where you want to store it.
232
+
1. Copy the `scheduler` binary file to the directory where you want to store it.
0 commit comments