Bulk upsert (create or update) asset criticality records
editBulk upsert (create or update) asset criticality records
editCreate or update asset criticality records for multiple entities.
If asset criticality records already exist for the entities specified in the request, this API overwrites those records with the specified values.
If asset criticality records don’t exist for the specified entities, new records are created.
Request URL
editPOST <kibana host>:<port>/api/asset_criticality/bulk
Request body
editA JSON object defining the asset criticality records.
Name | Type | Description | Required |
---|---|---|---|
|
Array |
Array of asset criticality records to be created or updated. The maximum number of records is 1000. |
Yes |
|
String |
The field that contains the entity ID. This must be either |
Yes |
|
String |
The ID (host name or user name) of the entity specified in the |
Yes |
|
String |
The asset criticality level to assign, which must be one of the following:
For example, you can assign |
Yes |
Example requests
editPOST /api/asset_criticality/bulk { "records": [ { "id_field": "host.name", "id_value": "my_host", "criticality_level": "medium_impact" }, { "id_field": "host.name", "id_value": "my_other_host", "criticality_level": "low_impact" } ] }
Response code
edit-
200
- Indicates a successful call.
Example response
editSuccessful response
{ "errors": [], "stats": { "successful": 2, "failed": 0, "total": 2 } }