Guide for Index Rollovers in AppDynamics Event Service
For event service deployments the index will rollover either when the average shard size breaches a threshold or when the age of the index exceeds the data retention period for the account/event type.
Regarding the newest releases of Event Service, it is also quite a common scenario in case of recent environment migration. After such migrations, indexes sometimes don't roll over automatically. This issue occurs if data older than the destination Event Service's retention period was migrated. In this particular case, the migrated data is beyond the retention period, so the new Event Service don't include it in the roll-over process.
In those cases, you can follow the instructions below to roll it over. The format of the curl request for index roll-over is a bit different for ES8 when compared to legacy ES2.
Before rolling over each index, please make sure that your cluster is in green status. Before and after rolling over an index, execute the following curl and ensure that the cluster is in "green" status, with no shards in unassigned status:
curl -s 'http://localhost:9200/_cat/health?v'
The template for index roll-over curl command is as follows:
curl -XPOST http://{host}:{port}/v1/admin/cluster/{cluster}/index/{index}/rollover -H"Authorization: Basic {key}" -H"Content-Type: application/json" -H"Accept: application/json" -d '{"numberOfShards": "2"}'
You need to fill up the following values manually in the above curl command:
- {host} - change with hostname, if you are running from the Event Service CLI, this can be set to "localhost",
- {port} - change to port event service is bined. By default 9080, refer to .properties file using "grep ad.dw.http.port events-service-api-store.properties",
- {cluster} - cluster name, this can be get from .properties file using "grep ad.es.cluster.name events-service-api-store.properties",
- {index} - Index to roll-over, the list of indexes cen be checked using the following curl http://localhost:9200/_cat/indices?v
- {key} - Base64 encoded ad.accountmanager.key.ops from events-service-api-store.properties file. On linux CLI, to get this value you can for example use: "echo -n {ad.accountmanager.key.ops} | base64"
