Reindex Activity Log Records Task
Learn how to reindex activity log records in a tenant.
This task allows you to reindex all activity log records in a tenant. By default, only the previous month's activity logs are reindexed due to performance and storage size considerations.
To reindex all activities in Elastic Search (ES), use the
activityFullReindex
parameter. Do take into consideration that this can cause
significant load on ES and performance degradation.
Requests
Role with tenant admin privileges required:
Name | Required | Description | |
---|---|---|---|
Headers | Authorization | Yes | Information about authentication access token in format "Bearer
<accessToken> " (see details in Authentication API . |
Path | tenantId | Yes | ID of the tenant to reindex activity log records. |
Query | skipEntitiesCount | No | The number of activity log records that will be skipped during the
reindexing. Default: 0 . |
updatedSince | No | Timestamp in UNIX format. If this parameter is specified, then
activity log records with a greater or equal timestamp
are reindexed. | |
activityFullReindex | No | If true , reindexes all activities in ES. If false or
not specified, only previous month activities are reindexed. | |
distributed | No | If set to true , the task is run in distributed mode
(see details in Distributed Mode). | |
taskPartsCount | No | Number of tasks that are created for distributed reindexing. Each
task reindexes its own part of objects, and all of them may be executed
on different API nodes. Recommended value: count of API nodes which can
execute the tasks. Note: This parameter is used only in distributed mode
( distributed =true ); otherwise,
it is ignored. |
Response
JSON Object representing a new task that has started.