Discovery Audit
Use these operations to interact with the discovered entities list in Cortex.
Required permissions
Your API key must have the Configure discovery audit events permission.
Operations
This report shows you recent changes in your environment that aren't reflected in Cortex, including newly created repositories, services, and resources that we discover from your integrations or which were deleted in the environment but corresponding Cortex entities are still present.
All requests to the Cortex API need to provide an Authorization: Bearer <token> header, where <token> is an API key created in the Settings page of your workspace.
Filter based on type of the event
Filter based on integration source
Flag to include ignored events in result
falseNumber of results to return per page, between 1 and 1000. Default 250.
250Page number to return, 0-indexed. Default 0.
0Successfully retrieved discovery audit report
The client has exceeded the rate limit by performing too many requests in a short period. Retry the request after a delay.
GET /api/v1/discovery-audit?pageSize=250&page=0 HTTP/1.1
Host: api.getcortexapp.com
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*
{
"events": [
{
"entity": {
"description": "text",
"name": "My Favorite Entity",
"tag": "my-favorite-entity",
"type": "service"
},
"isIgnored": true,
"mappingKey": {
"type": "AWS",
"arn": "arn"
},
"source": "AWS",
"type": "NEW_REPOSITORY"
}
],
"page": 1,
"total": 1,
"totalPages": 1
}Last updated
Was this helpful?