Skip to content

Commit

Permalink
Capitalization and phrasing
Browse files Browse the repository at this point in the history
  • Loading branch information
bradleycamacho committed May 9, 2022
1 parent 818109a commit 5935d9e
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions src/content/docs/errors-inbox/errors-inbox.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,9 @@ redirects:
---


import scoped from 'images/scopedBrowser.png';
import scopedBrowser from 'images/scopedBrowser.png';

import scoped from 'images/scopedOtel.png';
import scopedOtel from 'images/scopedOtel.png';

import errorsUi from 'images/errors-ui.png'

Expand Down Expand Up @@ -51,17 +51,17 @@ Ready to get started? Make sure you have a [New Relic account](https://newrelic.

Access to log management capabilities is limited by user type. See [user type capabilities](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type#user-type-capabilities).

## Use errors inbox directly from scoped views [#scoped]
## Use errors inbox from entity scoped views [#scoped]

Scoped views allow you to view errors for entities in browser, mobile, and [Open Telemetry](https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-introduction/#benefits). Access the errors inbox view for a specific entity by navigating to that entity in the browser or mobile monitoring view and selecting **Errors inbox** in the left nav.
Entity scoped views allow you to view errors for a single APM, browser, mobile, or [Open Telemetry](https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-introduction/#benefits) application. Access the errors inbox view for a specific entity by navigating to that entity in the browser or mobile monitoring view and selecting **errors inbox** in the left nav under **triage**.

<img
title="An image showing how to navigate to a scoped browser entity"
alt="This is an image of the main errors inbox UI inside a browser entity"
src={scopedBrowser}
/>

<figcaption>Traige errors for a browser or mobile entity by selecting **Errors inbox** in the left nav of the browser or mobile explorer.</figcaption>
<figcaption>Traige errors for a browser or mobile entity by selecting **errors inbox** in the left nav of the browser or mobile explorer.</figcaption>

NOTE: Please replace image above with new browser image provided on Slack channel

Expand All @@ -72,7 +72,7 @@ NOTE: Please replace image above with new browser image provided on Slack channe
src={scopedOtel}
/>

<figcaption>Traige errors for an OTel entity by selecting **Errors inbox** in the left nav of the Otel explorer.</figcaption>
<figcaption>Traige errors for an OTel entity by selecting **errors inbox** in the left nav of the Otel explorer.</figcaption>

NOTE: Please replace image above with new OTel image provided on Slack channel

Expand All @@ -81,7 +81,7 @@ NOTE: Please replace image above with new OTel image provided on Slack channel

To enable errors inbox, follow these steps. Afterwards, errors groups should start to appear in your inbox.

1. From [one.newrelic.com](https://one.newrelic.com) select **Errors inbox** from the top nav.
1. From [one.newrelic.com](https://one.newrelic.com) select **errors inbox** from the top nav.
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.
3. If you have no workloads set up, you will be prompted [to create one](/docs/new-relic-one/use-new-relic-one/workloads/use-workloads/) before you can use errors inbox.

Expand All @@ -94,7 +94,7 @@ Once you select your workload, your inbox should populate with error groups.
/>

<figcaption>
[one.newrelic.com](one.newrelic.com) > **More** > **Errors inbox**
[one.newrelic.com](one.newrelic.com) > **More** > **errors inbox**
</figcaption>

## Monitor errors
Expand Down

0 comments on commit 5935d9e

Please sign in to comment.