Merge pull request #2800 from ssugimotonr/patch-2

Added Slack Integration section and made other minor updates

src/content/docs/apm/apm-ui-pages/errors-inbox/errors-inbox.mdx

@@ -1,13 +1,13 @@
 ---
-title: 'Error inbox: one inbox for all your errors'
-metaDescription: "New Relic Errors inbox is an error tracking solution designed to put you in the driver’s seat when it comes to detecting, triaging, and resolving errors across your full application stack."
+title: 'Errors inbox: one inbox for all your errors'
+metaDescription: "New Relic Errors Inbox is an error tracking solution designed to put you in the driver’s seat when it comes to detecting, triaging, and resolving errors across your full application stack."
 redirects:
   - /docs/error-tracking
 ---
 
-New Relic Errors inbox is a single place to proactively detect, prioritize, and take action on all the errors before they impact customers. Receive alerts whenever a critical, customer-impacting error arises via your preferred communication channel.
+New Relic errors inbox is a single place to proactively detect, prioritize, and take action on all the errors before they impact customers. Receive alerts whenever a critical, customer-impacting error arises via your preferred communication channel.
 
-Resolve errors faster with errors from across your stack, including all APM, RUM (Browser), mobile, and serverless Lambda functions data, displayed on one screen. Errors are grouped to cut down on noise and collaborating across teams is easy with shared visibility to the same error data. 
+Resolve errors faster with errors from across your stack, including all APM, RUM (browser), ,obile, and serverless (AWS Lambda Functions) data, displayed on one screen. Errors are grouped to cut down on noise and collaborating across teams is easy with shared visibility to the same error data. 
 
 <Callout variant="important">
 Errors inbox is not available in the EU region.
@@ -18,29 +18,40 @@ Errors inbox is not available in the EU region.
 Errors inbox provides a unified error tracking experience to detect and triage errors:
 
 - View and triage issues across applications and services that your team cares about.
-- Proactive notifications with detailed error information.
+- Proactive notifications with detailed error information in Slack
 - Error profiles to show similarities between error events and surface the root cause.
-- Analyze errors in context of the full stack, and resolve errors with precision.
-- Triage and tackle errors, including APM, RUM, mobile, and serverless Lambda functions).
+- Analyze errors in context of the full stack and resolve errors with precision.
+- Triage and tackle errors, including APM, RUM, Mobile, and Serverless (AWS Lambda Functions).
 
-## Set up Errors inbox [#get-started]
+## Set up Errors Inbox [#get-started]
 
-To enable Errors inbox, follow these steps below. Afterwards, errors groups should start to appear in your inbox.
+To enable errors inbox, follow these steps below. Afterwards, errors groups should start to appear in your inbox.
 
-1. From [one.newrelic.com](one.newrelic.com) select **More** in the top right and click **Errors inbox** from the dropdown.
-2. If this is your first time accessing Errors inbox, you will be prompted to select a [workload](/docs/new-relic-one/use-new-relic-one/workloads/workloads-isolate-resolve-incidents-faster/) in the top left. 
+1. From [one.newrelic.com](one.newrelic.com) select **More** in the top right and click **Errors Inbox** from the dropdown.
+2. If this is your first time accessing errors inbox, you will be prompted to select a [workload](/docs/new-relic-one/use-new-relic-one/workloads/workloads-isolate-resolve-incidents-faster/) in the top left. 
 
-Once you select your workload, your inbox should populate with error groups. If you have no workloads set up, you will [need to create one](/docs/new-relic-one/use-new-relic-one/workloads/use-workloads/) before you can use the Errors inbox.
+Once you select your workload, your inbox should populate with error groups. If you have no workloads set up, you will [need to create one](/docs/new-relic-one/use-new-relic-one/workloads/use-workloads/) before you can use errors inbox.
+
+## Connect an inbox to Slack [#slack]
+
+Each inbox can be connected to a specific workspace and channel in Slack. To set this up, follow the steps below.
+
+1. If your Slack workspace does not have the [New Relic app](https://newrelic.slack.com/apps/AP92KQJS3-new-relic?tab=more_info) installed, do that first.
+2. From an inbox, select the **Inbox Settings** icon (looks like a gear) in the top right corner.
+3. Toggle the Slack button to "on" if it is "off".
+4. If no workspaces are available, click the "+" button to enable Slack with a one click Slack authentication.
+5. Once authenticated, you will be able to select a Workspace and specific Channel to send notifications to.
+6. Click "Test" to ensure messages are being sent to the right channel.
 
 ## Proactively monitor your errors [#monitor]
 
 ![This is an image of the main Errors inbox UI](./images/errors-ui.png "ui-main")
 
 <figcaption>[one.newrelic.com](one.newrelic.com) > **More** > ** Errors inbox**</figcaption>
 
-Once you've set up your Errors inbox, you can begin proactively monitoring all errors in your stack:
+Once you've set up your errors inbox, you can begin proactively monitoring all errors in your stack:
 
-1. **Error groups**: Your Errors inbox automatically groups your errors so you can easily review all the unique errors within your system.
+1. **Error groups**: Your errors inbox automatically groups your errors so you can easily review all the unique errors within your system.
 2. **Occurrences**: Your errors inbox displays the total number of occurences of each errors within the selected timeframe. The corresponding sparkline chart displays the total number of occurences per day over the selected timeframe.
 3. **Status**: You can set the status of an error by selecting the dropdown and choosing either **Unresolved**, **Resolve**, or **Ignore**. You can ignore errors to reduce noise, leave it unresolved, or proactively resolve the error.
 4. **Assign errors**: Assign errors directly to individuals.