Skip to main content
Version: 45.0.0

Migrate From a9s LogMe To a9s LogMe2

Strictly speaking, a direct migration between a9s LogMe and a9s LogMe2 service instances is not possible due to the incompatibilities between their underlying technologies (Elasticsearch 5 and OpenSearch 2 respectively).

However, due to the nature of these Data Services, it is possible to do a "migration by synchronization".


In order for this migration path to work it is necessary that your a9s LogMe and a9s LogMe2 service instance be able to reach your log source. Thus, this approach is not guaranteed to work with services instances running on different data centers and/or with different networking configurations.

In a nutshell, this can be achieved in two steps:

  • Spawn an a9s LogMe2 service instance that is equivalent, settings-wise, to your existing a9s LogMe service instance.
  • Configure both as a log sink for your log source and leave it running in parallel for about 30 days.

This approach ensures that after 30 days both service instances are fully synchronized, as data older than 30 days is automatically erased by default. After this is verified the a9s LogMe instance can be removed safely.

Synchronization Period

While the wording in this document describes the "migration by synchronization" in terms of the default values, the time frame is actually dependent on the configuration of your a9s LogMe service instance, more specifically the values you have set for the custom parameters curator_retention_unit and curator_retention_period. These values also define the value of the custom parameter ism_deletion_after in your a9s LogMe2 service instance.

For more detail, please refer to the Data Retention chapters in both our a9s LogMe and a9s LogMe2 documentation.