/beta/task-status API retention period is 3 months? (Entitlement Aggregations)

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

I have a use case where I want to report on entitlement count over time to show how much we’ve reduced the number. The only API endpoint I have found to use is get-task-status-list. The data within it is useful and allows me to see how many entitlements were scanned

{
   "attributes": {
            "eventId": 5418288,
            "total": "4322",
            "clusterCcgBuild": "984",
            "optimized": "3261",
            "appId": "2c9180877fdb6945017fe0b9ed8e5fef",
            "optimizedAggregation": "enabled",
            "updated": "1061"
        }
}

However, I’ve noticed today that the oldest record of task I’m able to retrieve is from 3 months ago, and my report that hasn’t refreshed yet shows data further back than 3 months, leading me to believe that there is a retention cutoff for this API endpoint or possibly the underlying data.

That said

  1. Is this working as designed?
  2. If so, is there a different API endpoint I can use to fulfill this use case?
2

I think it would make sense for the API documentation to mention the retention period, if existing, since it indeed has an impact on the results. Similar to the search API to fetch events and account activities.

3

@mcheek I confirmed that the data returned by get-task-status-list is only available for 90 days.

4

Yes, that would make sense, @angelo_mekenkamp!

I have created a ticket to add the 90 day data retention period to the API documentation (DEVREL-1741).

1 Like
5

I’m kinda bummed that’s the case cause it’s the only place you can get that level of detail for aggregations. There’s an audit event for account and entitlement aggregations but they don’t include data about the number of items scanned, created, deleted, updated, etc.

6

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.