---
title: "GET /resource_status"
method: GET
path: "/resource_status"
---

# GET /resource_status

`GET /resource_status`

## Request

- Base URL: `https://dev-cloud.acronis.com/api/alert_manager/v1`
- URL: `https://dev-cloud.acronis.com/api/alert_manager/v1/resource_status`
- Auth: OAuth 2
  - Authorization code: `https://dev-cloud.acronis.com/api/2/idp/authorize`
  - Client credentials
  - Password
  - Token URL: `https://dev-cloud.acronis.com/api/2/idp/token` scopes: `urn:acronis.com::alert_manager::viewer`

Fetches the resources' statuses that contain the alerts with the highest severity found for the resources. 
Resource with ID that was not found in `resourceId` parameter of any active alert considered to have the "ok" severity.

This endpoint may return multiple records for the same resource if it has multiple alerts with the same severity and the same creation time.

## Query parameters

- `id` string[]: IDs of the resources; if omitted, the response will contain statuses for all resources that have alerts. For resources with multiple IDs, the client must specify resource's IDs by using the `or()` operator: * Example: `id=or(ID3,ID4,ID5)` - looks for status of a single resource * Example: `id=ID1&id=or(ID3,ID4,ID5)&id=or(ID6,ID7)&id=ID8` - looks for status of four resources
- `embed_alert` boolean: If true, the entire alert object will be included in the response.

## Response `200`

List of alert grouping by resource IDs.

- object
  - `items` ResourceStatus[], required
    - `id` string, required: ID of the resource.
    - `severity` 'ok' | 'information' | 'warning' | 'error' | 'critical', required: The highest severity of the alert for the resource.
    - `alert` object: The information about the most recent alert with the highest severity.
      - `_sourceTimeStamp` integer
      - `falsePositive` boolean: Specifies whether alert is false positive or not.
      - `_source` string: An identifier of the alert producer.
      - `tenant` object, required
        - `id` string, required: An identifier of the alert owner.
        - `locator` string, required: Ascending hierarchy of tenant IDs separated by '/'.
      - `id` string, required
      - `createdAt` string, required: A client-side date and time when alert was created. Equals to the `receivedAt` field if not set by client.
      - `updatedAt` string, required: A date and time when the alert has been activated, deleted or dismissed.
      - `details` object, required: Copy of context is merged to details. Null if details and context are empty.
      - `category` string, required: Alert category.
      - `severity` 'ok' | 'information' | 'warning' | 'error' | 'critical', required: Alert severity level.
      - `deletedAt` string: A date and time when the alert was dismissed.
      - `receivedAt` string, required: A server-side date and time when the alert was received.
      - `type` string, required
      - `affinity` string: Alert synchronization affinity (e.g., agent ID).

## Other responses

- `401`: Request is refused because authentication parameters are invalid.
- `403`: A security error due to an issue with tenant security claim: invalid tenant in the access token, tenant resolution failed and etc.
- `414`: Too many resource IDs. For cloud deployment there is no limitation. For on-premise deployment known limits imposed by database engine are 32766 for SQLite and 2100 for MS SQL Server.

---

[API](https://skmtc.dev/acronis/apis/alert-manager-api.md) - [All operations](https://skmtc.dev/acronis/apis/alert-manager-api/llms.txt) - [OpenAPI document](https://skmtc.dev/acronis/apis/alert-manager-api/revisions/540eec169663?raw)