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/cloud/docker/docker-development.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ You can use the Docker environment to emulate the {{site.data.var.ece}} Integrat
48
48
49
49
-**[{{site.data.var.mcd-package}} GitHub repository]**–Visit the GitHub repository to read discussions about current issues, check current development, and submit issues or pull requests to improve the project.
50
50
51
-
-**Magento Cloud Community Engineering demos**–Magento hosts Cloud demo session where you can learn about developing Magento on the Cloud platform, including information about local development with {{site.data.var.mcd-prod}}}. For a schedule and recordings of previous demos, see the [Magento Cloud Community Engineering Demo Schedule].
51
+
-**Magento Cloud Community Engineering demos**–Magento hosts Cloud demo session where you can learn about developing Magento on the Cloud platform, including information about local development with {{site.data.var.mcd-prod}}. For a schedule and recordings of previous demos, see the [Magento Cloud Community Engineering Demo Schedule].
Copy file name to clipboardExpand all lines: src/cloud/project/new-relic.md
+31-33Lines changed: 31 additions & 33 deletions
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ functional_areas:
8
8
- Services
9
9
---
10
10
11
-
{{ site.data.var.ece }} projects include access to New Relic services to help manage, monitor, and troubleshoot your applications and infrastructure by collecting, viewing, and analyzing data from your {{ site.data.var.ece }} project.
11
+
{{ site.data.var.ece }} projects include access to the following New Relic services to help manage, monitor, and troubleshoot your applications and infrastructure by collecting, viewing, and analyzing data from your {{ site.data.var.ece }} project.
12
12
13
13
-[New Relic APM](#new-relic-apm) (Pro and Starter)
14
14
-[New Relic Infrastructure](#new-relic-infrastructure) (Pro, Production environment only)
@@ -22,7 +22,7 @@ functional_areas:
22
22
-**Database query monitoring**—Locate and monitor database queries affecting performance.
23
23
-**App Map**—View all application dependencies within your Magento site, extensions, and external services.
24
24
-**Apdex scores**—Evaluate performance and create alerts that identify issues and notify you when they occur, such as site performance affected by a flash sale or web event. See [Apdex score].
25
-
-**Managed Alerts for Magento Commerce**–Use this New Relic alert policy to monitor application and infrastructure performance based on industry best practices. See [Monitor performance with the Magento alert policy](#monitor-performance-with-managed-alerts).
25
+
-**Managed Alerts for Magento Commerce**–Use this New Relic alert policy to monitor application and infrastructure performance based on industry best practices. See [Monitor performance with the Managed Alerts for {{ site.data.var.ee }} alert policy](#monitor-performance-with-managed-alerts).
26
26
27
27
Your {{site.data.var.ece}} project includes the software for the New Relic APM service along with a license key. You do not need to purchase or install any additional software.
28
28
@@ -31,7 +31,7 @@ Your {{site.data.var.ece}} project includes the software for the New Relic APM s
31
31
{{site.data.var.ece}} Pro projects include the [New Relic Infrastructure (NRI)][New Relic infrastructure] service, which automatically connects with the application data and performance analytics to provide dynamic server monitoring. This service is available on Production and Staging environments.
32
32
33
33
{:.bs-callout-info}
34
-
For Pro accounts, if New Relic APM is not installed on the Staging and Production environments or New Relic Infrastructure is not available in the Production environment, submit a [support ticket]({{ site.baseurl }}/cloud/trouble/trouble.html) to request installation.
34
+
For Pro accounts, if New Relic APM is not installed on the Staging and Production environments or New Relic Infrastructure is not available in the Production environment, [submit a Magento Support ticket] to request installation.
35
35
36
36
## New Relic Logs
37
37
@@ -52,7 +52,7 @@ As soon as your project is connected to New Relic, you can use the New Relic Log
52
52
53
53
See [View and analyze logs](#view-and-analyze-log-data).
54
54
55
-
## Manage your New Relic account
55
+
## Manage New Relic account
56
56
57
57
When Magento provisions your {{site.data.var.ece}} project, the License Owner receives an email from New Relic with credentials and instructions for accessing the New Relic account. If you did not receive the email, use the License Owner email address to [reset the New Relic password].
58
58
@@ -80,13 +80,13 @@ To add a user:
80
80
81
81
1. Ask the new user to check their email for a New Relic notification with account information.
82
82
83
-
## Set up the New Relic service
83
+
## Set up New Relic
84
84
85
85
Pro environments are preconfigured to use New Relic services.
86
86
87
87
For Starter environments, you must check the `.magento.app.yaml` file to verify that the `runtime` section includes the New Relic extension. If the extension has not been configured, add the following:
88
88
89
-
> .magento.app.yaml
89
+
> `.magento.app.yaml`
90
90
91
91
```yaml
92
92
runtime:
@@ -95,31 +95,30 @@ runtime:
95
95
```
96
96
97
97
{:.bs-callout-warning}
98
-
If you upgrade the PHP version on your {{site.data.var.ece}} project, you must submit a Magento Support ticket to update the New Relic service.
98
+
If you upgrade the PHP version on your {{site.data.var.ece}} project, you must [submit a Magento Support ticket] to update the New Relic service.
99
99
100
100
## Connect to New Relic
101
101
102
-
To connect a Cloud environment to New Relic, you must add the New Relic license key to the environment.
102
+
To connect a Cloud environment to New Relic, add the New Relic license key to the environment.
103
103
104
104
- For Pro accounts, Magento adds the license key to your Cloud environments during the provisioning process. You can log in to your New Relic account to verify connectivity between your Magento Commerce site and New Relic.
105
105
106
106
- For Starter accounts, you have a New Relic license key that supports up to three environments. You must add the key to your environment configurations manually. The license key is not pre-provisioned on Starter environments.
107
107
108
108
### Configure New Relic for Starter environments
109
109
110
-
For Starter environments, you must add the New Relic license key to the environment configuration to enable the New Relic integration. We recommend adding the key to the Staging and Production (master) environments and one other environment of your choice. Only the New Relic license key is required for configuration. You can find information about additional configuration options in the [New Relic reporting] topic in the _Magento User Guide_.
110
+
For Starter environments, enable the New Relic integration by adding the New Relic license key to the environment configuration. We recommend adding the key to the Staging and Production (master) environments and one other environment of your choice. Only the New Relic license key is required for configuration. You can find information about additional configuration options in the [New Relic reporting] topic in the _Magento Commerce User Guide_.
111
111
112
112
{:.bs-callout-warning}
113
113
Updating the environment configuration triggers a redeployment, which takes your site offline until deployment completes. For Production environments, we recommend completing this work during off-peak hours to avoid service disruptions. See [Working with variables].
114
114
115
-
{:.procedure}
116
-
Prerequisites
115
+
**Prerequisites:**
117
116
118
117
- Log in credentials for the Magento account page, or for the New Relic account associated with your project
119
118
- [Admin level access]({{site.baseurl}}/cloud/project/user-admin.html) to the Starter environments to configure, or credentials to access the [Magento Admin](https://docs.magento.com/m2/ce/user_guide/system/permissions.html) for the environment.
120
119
121
120
{:.procedure}
122
-
To configure New Relic on a Starter environment:
121
+
To configure New Relic for Starter environments:
123
122
124
123
1. Find your New Relic license key from your Magento Cloud account page, or [from your New Relic account page]:
125
124
@@ -133,7 +132,7 @@ To configure New Relic on a Starter environment:
133
132
134
133
- Copy the license key.
135
134
136
-
1. Add the New Relic license key to an environment using the Magento Cloud CLI, or [add it from the Magento Admin]:
135
+
1. Add the New Relic license key to an environment using the Magento Cloud CLI, or [add it from the Magento Admin].
137
136
138
137
- Change to the environment that needs the license key.
139
138
@@ -145,7 +144,7 @@ To configure New Relic on a Starter environment:
145
144
146
145
1. [Log in to New Relic][New Relic login] to verify that you can view data from the Magento Cloud environment. (See [Investigate performance](#investigate-performance).)
147
146
148
-
### Remove New Relic license key from a Starter environment
147
+
### Remove license key from a Starter environment
149
148
150
149
If three active Starter environments already use the same New Relic license key, and you want to configure New Relic reporting on a different environment, you must remove the key from one of the configured environments before you can reuse it.
151
150
@@ -250,29 +249,27 @@ For further information and examples, see [Introduction to New Relic Logs][New R
250
249
251
250
### Monitor performance with Managed Alerts
252
251
253
-
Adobe provides the Managed Alerts for {{ site.data.var.ee }} alert policy on Cloud Pro Production environments to track the following metrics:
254
-
255
-
- [Apdex score]
256
-
- error rate
257
-
- disk space (available on Pro Production environments only)
258
-
- CPU usage
259
-
- memory usage
252
+
Adobe provides the Managed Alerts for {{ site.data.var.ee }} alert policy to track performance metrics.
253
+
Based on industry best practices, the policy includes a collection of alerts that set thresholds to trigger warning and critical notifications when site infrastructure or application issues affect performance. The Managed Alerts policy tracks the following metrics on Production environments only:
260
254
261
-
Based on industry best practices, this policy is a collection of alerts that set thresholds for warning and critical conditions that affect performance.
When your site experiences an infrastructure or application issue that triggers an alert threshold, New Relic sends alert notifications so that you can proactively address the issue. See [Managed Alerts for Magento Commerce][] in the _Magento Help Center_ for details about each alert type and troubleshooting steps to resolve the issues that triggered the alert.
264
-
265
-
{:.bs-callout-warning}
266
-
To use this policy and get notified when an issue on your site triggers an alert condition, you must configure at least one notification channel to receive the alert notifications.
263
+
When site infrastructure or application conditions trigger an alert threshold, New Relic sends alert notifications so that you can proactively address the issue. See [Managed Alerts for Magento Commerce] in the _Magento Help Center_ for details about alert thresholds and troubleshooting steps to resolve the issues that triggered the alert.
267
264
268
265
{:.bs-callout-info}
269
266
For Pro Staging and Integration environments and Starter environments, use [Health notifications] to monitor disk space.
270
267
271
-
{:.procedure}
272
-
Prerequisites
268
+
**Prerequisites:**
273
269
274
270
- Credentials to log in to the [New Relic account] for your Cloud project
275
271
- Verify that your Cloud environment is [connected to New Relic](#connect-to-new-relic)
272
+
- Configure at least one [notification channel](#configure-notification-channels) to receive the alert notifications
276
273
277
274
{:.procedure}
278
275
To review the Managed Alerts for {{ site.data.var.ee }} policy:
@@ -294,15 +291,15 @@ To review the Managed Alerts for {{ site.data.var.ee }} policy:
If the policy is missing, submit a Magento support ticket. Include your project ID in the ticket. The policy is available on Pro and Starter Production environments only.
294
+
If the Managed Alerts for {{ site.data.var.ee }} alert policy is not available, see [Managed Alerts for Magento Commerce][] in the _Magento Help Center_.
298
295
299
296
1. Click **Managed Alerts for Magento Commerce** to review the alert conditions defined in the policy.
To use the Managed Alerts for Magento Commerce policy to monitor your Production sites, you must configure at least one notification channel and map it to the alert policy.
302
+
To use Managed Alerts for {{ site.data.var.ee }} to monitor your Production sites, you must configure at least one notification channel and map it to the alert policy.
306
303
307
304
Notifications about performance issues go to all channels associated with an alert policy when conditions on the application or infrastructure trigger an alert. You also receive notifications when an issue is acknowledged and closed.
308
305
@@ -350,7 +347,7 @@ See the following New Relic documentation topics for additional information:
350
347
{:.bs-callout-warning}
351
348
The alerts in the Managed Alerts for Magento Commerce policy have default notification channels configured to notify Magento teams that support {{ site.data.var.ece }} customers. Do not modify the configuration for these default channels, and do not remove any alert policies assigned to them.
352
349
353
-
### Create Alert Policies
350
+
### Create alert policies
354
351
355
352
Do not modify any alerts included in the Managed Alerts for Magento Commerce policy. We update and improve the alert conditions in this policy over time, which overwrites any customizations you add to the policy.
356
353
@@ -377,7 +374,7 @@ See [Alerts concepts and workflow] in the New Relic documentation for more detai
[Troubleshoot performance using New Relic]: https://support.magento.com/hc/en-us/articles/360042149832#low_user_satisfaction
394
390
[reset the New Relic password]: https://rpm.newrelic.com/forgot_password
391
+
[submit a Magento Support ticket]: {{ site.baseurl }}/cloud/trouble/trouble.html
392
+
[Troubleshoot performance using New Relic]: https://support.magento.com/hc/en-us/articles/360042149832#low_user_satisfaction
395
393
[Update the account owner]: https://docs.newrelic.com/docs/accounts/accounts/roles-permissions/change-account-owner
396
394
[Update policies or conditions]: https://docs.newrelic.com/docs/alerts/new-relic-alerts/configuring-alert-policies/update-or-disable-policies-conditions
397
395
[View your license key]: https://docs.newrelic.com/docs/accounts/install-new-relic/account-setup/license-key#finding
0 commit comments