Skip to content

Commit b7d47a5

Browse files
committed
renames
1 parent b4a7a13 commit b7d47a5

File tree

2 files changed

+34
-13
lines changed

2 files changed

+34
-13
lines changed

src/content/docs/errors-inbox/error-impacted.mdx

Lines changed: 34 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -50,40 +50,61 @@ You can review how New Relic processes custom attributes by reading our doc abou
5050

5151
Impact metrics for error groups are recorded as [Metric data types](/docs/data-apis/understand-data/metric-data/metric-data-type/) with specific metric names:
5252

53-
- **Users impacted**: `newrelic.error.group.userImpact`
54-
- **Sessions impacted**: `newrelic.error.group.sessionImpact`
55-
- **Devices impacted**: `newrelic.error.group.deviceImpact`
53+
<CollapserGroup>
54+
<Collapser
55+
className="freq-link"
56+
id="users"
57+
title="Users impacted"
58+
>
5659

57-
You can query users impacted with the following NRQL string:
60+
You can query the number of users impacted using `newrelic.error.group.userImpact` as metric name in NRQL queries:
5861

5962
```sql
6063
SELECT uniqueCount(newrelic.error.group.userImpact)
6164
FROM Metric
6265
WHERE metricName='newrelic.error.group.userImpact'
6366
```
6467

65-
The metric captures the approximate number of unique users in the time period selected. Additional attributes provided by the `userImpact` metric which can be used in a `FACET` clause are `error.group.guid`, `entity.guid`.
68+
This NRQL query metric captures the approximate number of unique users in the time period selected. Additional attributes provided by the `userImpact` metric which can be used in a `FACET` clause are `error.group.guid`, `entity.guid`.
6669

67-
### Query sessions impacted (Browser entities)
70+
</Collapser>
6871

69-
For browser applications, you can query sessions impacted:
72+
<Collapser
73+
className="freq-link"
74+
id="sessions"
75+
title="Sessions impacted"
76+
>
77+
78+
You can query the number of sessions impacted using `newrelic.error.group.sessionImpact` as metric name in NRQL queries:
7079

7180
```sql
7281
SELECT uniqueCount(newrelic.error.group.sessionImpact)
7382
FROM Metric
7483
WHERE metricName='newrelic.error.group.sessionImpact'
7584
```
7685

77-
### Query devices impacted (Mobile entities)
86+
</Collapser>
87+
88+
<Collapser
89+
className="freq-link"
90+
id="devices"
91+
title="Devices impacted"
92+
>
7893

79-
For mobile applications, you can query devices impacted:
94+
You can query the number of devices impacted using `newrelic.error.group.deviceUuidImpact` as metric name in NRQL queries:
8095

8196
```sql
82-
SELECT uniqueCount(newrelic.error.group.deviceImpact)
97+
SELECT uniqueCount(newrelic.error.group.deviceUuidImpact)
8398
FROM Metric
84-
WHERE metricName='newrelic.error.group.deviceImpact'
99+
WHERE metricName='newrelic.error.group.deviceUuidImpact'
85100
```
86101

102+
</Collapser>
103+
104+
</CollapserGroup>
105+
106+
107+
87108
## Alert on impact metrics [#alert]
88109

89110
By creating an [NRQL alert condition](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-alert-conditions/), developers can trigger <InlinePopover type="alerts"/> when the scope of errors exceeds a threshold. You can create alerts for any of the impact metrics:
@@ -129,9 +150,9 @@ AND entity.guid='YOUR_BROWSER_ENTITY_GUID' FACET error.group.guid TIMESERIES
129150
For mobile applications, you can create alerts based on devices impacted:
130151

131152
```sql
132-
SELECT uniqueCount(newrelic.error.group.deviceImpact)
153+
SELECT uniqueCount(newrelic.error.group.deviceUuidImpact)
133154
FROM Metric
134-
WHERE metricName='newrelic.error.group.deviceImpact'
155+
WHERE metricName='newrelic.error.group.deviceUuidImpact'
135156
AND entity.guid='YOUR_MOBILE_ENTITY_GUID' FACET error.group.guid TIMESERIES
136157
```
137158

File renamed without changes.

0 commit comments

Comments
 (0)