Get workloads that need attention

get

https://api.doit.com/attribute/v1/workloads/signals

Returns three lists of workloads that need attention, grouped by workload name and type.
Each list has every workload that meets its rules, ranked:

spike: cost grew a lot against the week before.
new: workloads first seen in the last two weeks with real cost.
network: network cost grew a lot against the week before (the same rules as spike,
applied to network cost).

The windows are fixed UTC days and do not depend on any date range: the current window is
today minus 8 days to today minus 2 days, and the previous window is the 7 days before it.
window and thresholds in the response give the exact dates and rules. Use this for
"what changed" or "what should I look at". To get the matching rows or totals over your own
date range, pass signal=spike|new|network to queryAttributeWorkloadsTable,
queryAttributeWorkloadsStats or queryAttributeWorkloadsOverTime.

Freemium customers (no paid Attribute plan) see network cost only, so all three lists use
network cost for them.

Authenticate with Authorization: Bearer <token>. Omit X-Tenant-Id when the credential
resolves to one customer. When the credential can act on several customers, send
X-Tenant-Id: <tenant-id> to select one.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Headers

X-Tenant-Id

string

Customer (tenant) ID for the request. This is separate from authentication: you still pass your personal or service account API token in the Authorization header (Bearer <token>). See Get Started.

When to omit (most callers): If your personal or service account token belongs to a single customer, omit this header. The API resolves that customer from the token.

When to send: If your credential can access more than one customer, set X-Tenant-Id to the customer ID you want to act on. A service account can select an active direct or nested descendant of its home customer; the endpoint's normal permissions, entitlements, and resource-ownership checks still apply. A service-account target outside that customer subtree returns 403 Forbidden. Prefer this header over the legacy customerContext query parameter, which only applies to legacy API keys and is ignored by personal and service account tokens.

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Responses

Language

Credentials

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

application/problem+json

200OK - The three signal lists, their windows and thresholds.

401Unauthorized - The Authorization: Bearer <token> header is missing, the token is not valid, or the person behind the token has no email address. Code: unauthorized.

404Not Found - route_not_found when the path or HTTP method is not one of the Attribute Workloads operations. not_found when the workloadId does not decode: copy it unchanged from a workload row of queryAttributeWorkloadsTable.

409Conflict - The customer is not set up in Attribute yet (attribute_customer_not_provisioned) or its Attribute setup needs a fix by DoiT (attribute_tenant_reconciliation_required). Retrying does not help; contact DoiT support.

500Internal Server Error - Unexpected error in the Attribute service (upstream_error). Retry with backoff.

502Bad Gateway - A service behind the gateway did not answer: token check (auth_unavailable) or the Attribute service (upstream_unavailable), or the Attribute service refused the gateway (upstream_error). Retry with backoff.

503Service Unavailable - The Attribute integration is turned off (integration_disabled), the token check is unavailable (auth_unavailable), or the permission check is unavailable (authorization_unavailable). Retry later.