Submit Job to List Alerts
POST/alert/jobs
Submits a job to generate an alerts list that matches the constraints in the body parameters and is downloadable in JSON format. Returns the job ID and job submission status.
Filter model fields specific to pagination (sortBy, limit, and pageToken) do not apply to this request, even though the body parameters include them.
The fields body parameter allows you to request specific fields from the alert payload. These fields are separate from the filters you specify. The following are valid fields items.
alert.id
alert.status
alert.time
cloud.account
cloud.accountId
cloud.region
resource.id
resource.name
policy.name
policy.type
policy.severity
The filters body parameter enables you to narrow your request for alerts. See List Alert Filters for an API request to list all the valid filters.
Rate Limits
The following rate limits apply:
- Request rate limit: 2/sec
- Burst limit: 10/sec
Request
- application/json; charset=UTF-8
Body
required
Model for Filter
- Array [
- ]
- RelativeTimeRangeConfigModel
- AbsoluteTimeRangeConfigModel
- ToNowTimeRangeConfigModel
Detailed
Array of specific fields to return
filters object[]
Filtering parameters.
For filter names, refer to List Filters API.
For filter values, refer to List filter suggestions.
The only exception is resource.tagv2 filter name, provide filter value for it in the following format: "{"key":"'CustomerTagKey'","value":"'CustomerTagValue'"}"
Name
Possible values: [=
]
Operator
Value
For asset or data inventory only. Group returned items by cloud.type, cloud.service, cloud.region, cloud.account, and/or resource.type
Maximum number of items to return. When data is paginated, maximum number of items per page.The maximum cannot exceed 10,000. The default is 10,000.
The number of items to skip before selecting items to return. Default is zero
Setting this pagination Token to the nextPageToken from a response object returns the next page of data
Array of sort properties. Append :asc or :desc to the key to sort by ascending or descending order respectively. Example sort properties are id:asc and timestamp:desc
timeRange object
See the Time Range Model for details.
Possible values: [BACKWARD
, FORWARD
]
Direction in which to count time. Default = BACKWARD
value objectrequired
Model for RelativeTimeDuration
Number of time units
Possible values: [minute
, hour
, day
, week
, month
, year
]
Time unit
value objectrequired
Model for Time
End timestamp
Start timestamp
Possible values: [MINUTE
, HOUR
, DAY
, WEEK
, MONTH
, YEAR
, EPOCH
, LOGIN
]
Time range object
Responses
- 200
- 400
- 429
successful operation
- application/json; charset=UTF-8
- Schema
- Example (from schema)
Schema
Job creator
Creation timestamp
Download URI
Job ID
Timestamp for last modified
Record Count
Possible values: [COMPLETED
, FAILED
, IN_PROGRESS
, READY_TO_DOWNLOAD
, SUBMITTED
]
Job status
Status URI
Time taken to complete the job
{
"createdBy": "string",
"createdOn": 0,
"downloadUri": "string",
"id": "string",
"lastModified": 0,
"recordCount": 0,
"status": "COMPLETED",
"statusUri": "string",
"timeTaken": 0
}
internal_error
Too Many Requests