---
title: "Get the impact of an error tracking issue"
method: GET
path: "/api/v2/error-tracking/issues/{issue_id}/impact"
tags: ["Error Tracking"]
---

# Get the impact of an error tracking issue

`GET /api/v2/error-tracking/issues/{issue_id}/impact`

## Request

- Base URL: `https://api.datadoghq.com`
- URL: `https://api.datadoghq.com/api/v2/error-tracking/issues/{issue_id}/impact`
- Auth: one of:
  - API key in header `DD-API-KEY` and API key in header `DD-APPLICATION-KEY`
  - OAuth 2
    - Authorization code: `/oauth2/v1/authorize`
    - Token URL: `/oauth2/v1/token` scopes: `error_tracking_read`

Get an issue's impact over a time window: its error counts by source, and the users, sessions, accounts,
RUM views, and endpoints it affects most.
Returns 403 if the caller lacks the `error_tracking_read` permission or does not have access to the issue's
data.

## Path parameters

- `issue_id` string, required

## Query parameters

- `filter[from]` integer, required
- `filter[to]` integer, required

## Response `200`

OK

- IssueImpactResponse: Response containing the impact of an error tracking issue.
  - `data` IssueImpact, required: The impact of an issue over the requested time window.
    - `attributes` IssueImpactAttributes, required: The issue's errors in the time window, and the users, sessions, accounts, views, and endpoints they affect.
      - `accounts` IssueImpactAccounts, required: Accounts whose users are affected by the issue.
        - `distinct_count` integer, required: Number of distinct accounts affected by the issue in the time window.
        - `top` IssueImpactAccount[], required: Up to five accounts with the most errors, most affected first.
          - `error_counts` IssueImpactErrorCounts, required: Number of errors reported by each source. Several sources can report the same error, such as an APM span and a log, so the counts overlap: don't add them together.
            - `apm` integer, required: Number of errors reported by APM.
            - `llmobs` integer, required: Number of errors reported by Agent Observability.
            - `logs` integer, required: Number of errors reported by Log Management.
            - `rum` integer, required: Number of errors reported by RUM.
          - `id` string, required: Account ID, from the `account.id` attribute.
          - `name` string: Account name, if available.
          - `significant` boolean, required: Whether the entry stands out as a likely driver of the issue, because it accounts for most of the issue's errors or for far more errors than the other listed entries.
      - `endpoints` IssueImpactEndpoints, required: Endpoints whose traces have the issue's errors, identified by each trace's root span.
        - `distinct_count` integer, required: Number of distinct endpoints affected by the issue in the time window.
        - `top` IssueImpactEndpoint[], required: Up to five endpoints with the most errors, most affected first.
          - `error_counts` IssueImpactErrorCounts, required: Number of errors reported by each source. Several sources can report the same error, such as an APM span and a log, so the counts overlap: don't add them together.
            - `apm` integer, required: Number of errors reported by APM.
            - `llmobs` integer, required: Number of errors reported by Agent Observability.
            - `logs` integer, required: Number of errors reported by Log Management.
            - `rum` integer, required: Number of errors reported by RUM.
          - `resource_name` string, required: Resource name of the trace's root span.
          - `service` string, required: Service of the trace's root span.
          - `significant` boolean, required: Whether the entry stands out as a likely driver of the issue, because it accounts for most of the issue's errors or for far more errors than the other listed entries.
      - `error_counts` IssueImpactErrorCounts, required: Number of errors reported by each source. Several sources can report the same error, such as an APM span and a log, so the counts overlap: don't add them together.
        - `apm` integer, required: Number of errors reported by APM.
        - `llmobs` integer, required: Number of errors reported by Agent Observability.
        - `logs` integer, required: Number of errors reported by Log Management.
        - `rum` integer, required: Number of errors reported by RUM.
      - `sessions` IssueImpactSessions, required: RUM sessions where the issue occurred.
        - `distinct_count` integer, required: Number of distinct sessions where the issue occurred in the time window.
        - `top` IssueImpactSession[], required: Up to five sessions with the most errors, most affected first.
          - `error_counts` IssueImpactErrorCounts, required: Number of errors reported by each source. Several sources can report the same error, such as an APM span and a log, so the counts overlap: don't add them together.
            - `apm` integer, required: Number of errors reported by APM.
            - `llmobs` integer, required: Number of errors reported by Agent Observability.
            - `logs` integer, required: Number of errors reported by Log Management.
            - `rum` integer, required: Number of errors reported by RUM.
          - `id` string, required: Session identifier.
          - `significant` boolean, required: Whether the entry stands out as a likely driver of the issue, because it accounts for most of the issue's errors or for far more errors than the other listed entries.
      - `users` IssueImpactUsers, required: Users affected by the issue.
        - `distinct_count` integer, required: Number of distinct users affected by the issue in the time window.
        - `top` IssueImpactUser[], required: Up to five users with the most errors, most affected first.
          - `error_counts` IssueImpactErrorCounts, required: Number of errors reported by each source. Several sources can report the same error, such as an APM span and a log, so the counts overlap: don't add them together.
            - `apm` integer, required: Number of errors reported by APM.
            - `llmobs` integer, required: Number of errors reported by Agent Observability.
            - `logs` integer, required: Number of errors reported by Log Management.
            - `rum` integer, required: Number of errors reported by RUM.
          - `id` string, required: User ID, from the `usr.id` attribute.
          - `name` string: User name or email, if available.
          - `significant` boolean, required: Whether the entry stands out as a likely driver of the issue, because it accounts for most of the issue's errors or for far more errors than the other listed entries.
      - `views` IssueImpactViews, required: RUM views where the issue occurred.
        - `distinct_count` integer, required: Number of distinct view names where the issue occurred in the time window.
        - `top` IssueImpactView[], required: Up to five views with the most errors, most affected first.
          - `affected` IssueImpactViewCounts, required: Distinct users, accounts, sessions, and view instances on a view. `affected` counts only those with the issue's errors. `baseline` counts all users, accounts, sessions, and view instances on the view in the time window. It is absent when RUM has no data for the view.
            - `accounts` integer, required: Number of distinct accounts.
            - `sessions` integer, required: Number of distinct sessions.
            - `users` integer, required: Number of distinct users.
            - `views` integer, required: Number of distinct view instances.
          - `baseline` IssueImpactViewCounts: Distinct users, accounts, sessions, and view instances on a view. `affected` counts only those with the issue's errors. `baseline` counts all users, accounts, sessions, and view instances on the view in the time window. It is absent when RUM has no data for the view.
            - `accounts` integer, required: Number of distinct accounts.
            - `sessions` integer, required: Number of distinct sessions.
            - `users` integer, required: Number of distinct users.
            - `views` integer, required: Number of distinct view instances.
          - `error_counts` IssueImpactErrorCounts, required: Number of errors reported by each source. Several sources can report the same error, such as an APM span and a log, so the counts overlap: don't add them together.
            - `apm` integer, required: Number of errors reported by APM.
            - `llmobs` integer, required: Number of errors reported by Agent Observability.
            - `logs` integer, required: Number of errors reported by Log Management.
            - `rum` integer, required: Number of errors reported by RUM.
          - `name` string, required: View name.
          - `significant` boolean, required: Whether the entry stands out as a likely driver of the issue, because it accounts for most of the issue's errors or for far more errors than the other listed entries.
    - `id` string, required: Identifier of the issue.
    - `type` 'error_tracking_issue_impact', required: Type of the object.

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found
- `429`: Too many requests

## Changes

- **2026-11-16** `6f7f45b8df10`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/changes/api/v2/error-tracking/issues/:issue_id/impact/get.md)

---

[API](https://skmtc.dev/datadog/apis/datadog-api-v2-collection.md) - [All operations](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/llms.txt) - [OpenAPI document](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/revisions/d0ad57792f3c?raw)
