list-cloud-incidents
dci list-cloud-incidents [flags]
Returns a list of all the active and historical cloud incidents for Google Cloud and Amazon Web Services. Incidents are returned in reverse chronological order by default.
CLI default view
dci list-cloud-incidents presents a curated table by default:
- Columns:
title,platform,product,status, andcreated (UTC)(fromcreateTime). - In interactive tables,
created (UTC)renders in your local timezone and is titledcreated (local); machine formats, agent mode, and--utckeep UTC — see Timestamps and timezones. --output jsonand explicit-C/--fieldsselections return the raw fields documented below.
Flags
--max-results: (integer format:int64 default:50)
--page-token: (string)
--filter: (string)
--min-creation-time: (string)
--max-creation-time: (string)
Output
OK - The request succeeded.
By default dci renders the result as a table. Use --output json to get the full structure described below — see Output formats.
| Field | Type | Description |
|---|---|---|
incidents | array of object | Array of cloud incidents |
incidents[].createTime | integer (int64) | The creation time of this cloud incident, in milliseconds since the epoch. |
incidents[].id | string | The unique cloud incident identifier. |
incidents[].platform | string | The Cloud Platform. One of: "google-cloud", "amazon-web-services", "microsoft-azure". |
incidents[].product | string | The name of the product affected by the cloud incident |
incidents[].status | string | The Status of the issue One of: "active", "archived". |
incidents[].title | string | Cloud incident name as provided by the cloud platform vendor |
pageToken | string | Page token, returned by a previous call, to request the next page of results |
rowCount | integer (int64) | Cloud incidents rows count |
Raw JSON schema
{
"type": "object",
"properties": {
"incidents": {
"type": "array",
"description": "Array of cloud incidents",
"items": {
"type": "object",
"description": "Summary information for a cloud incident.",
"properties": {
"createTime": {
"type": "integer",
"description": "The creation time of this cloud incident, in milliseconds since the epoch.",
"format": "int64"
},
"id": {
"type": "string",
"description": "The unique cloud incident identifier."
},
"platform": {
"type": "string",
"description": "The Cloud Platform.",
"enum": [
"google-cloud",
"amazon-web-services",
"microsoft-azure"
]
},
"product": {
"type": "string",
"description": "The name of the product affected by the cloud incident"
},
"status": {
"type": "string",
"description": "The Status of the issue",
"enum": [
"active",
"archived"
]
},
"title": {
"type": "string",
"description": "Cloud incident name as provided by the cloud platform vendor"
}
}
}
},
"pageToken": {
"type": "string",
"description": "Page token, returned by a previous call, to request the next page of results"
},
"rowCount": {
"type": "integer",
"description": "Cloud incidents rows count",
"format": "int64"
}
}
}
Errors
On failure, dci prints a single error message — with a hint when one is available — and exits with a typed code your scripts can branch on. See Errors and exit codes for the full contract.
| HTTP status | Exit code | Error code | Meaning |
|---|---|---|---|
| 400 | 30 | VALIDATION_ERROR | The arguments or request body were rejected. Review the command's flags and payload. |
| 401 | 10 | AUTHENTICATION_FAILED | Not signed in, or the API token is invalid. Run dci login or check DCI_API_KEY. |
| 403 | 11 | PERMISSION_DENIED | The DoiT user or the active customer context does not have access. |
| 404 | 20 | RESOURCE_NOT_FOUND | The requested resource does not exist. Check the identifier argument. |
Aliases: list-known-issues