On-Premises Events Migration - All-In-One

[NOTE: This guide is intended for environments that are running a single-server “all-in-one” installation of On-Premises Sysdig Monitor. Environments running a “multi-server distributed” installation should refer to the multi-server distributed guide instead.]

To improve search capabilities and offer improved performance, beginning with version 494 of On-Premises Sysdig Monitor, Elasticsearch is used to store Custom Events. In order to complete an update to version 494 or newer, it is mandatory to migrate previously-stored events into Elasticsearch. Follow the steps below to complete the migration.

Prerequisites

Must be up & running Sysdig Monitor On-Premises version 439 or older

Step 1 - Verify existing events

Log in to the Sysdig Monitor application and familiarize yourself with recent events by navigating to the page Events > Custom Events. You may want to take a screenshot so you can refer to it later when confirming the success of the migration.

Step 2 - Update Sysdig Monitor version

Using the Admin console, click from the  tab to update the Sysdig Monitor application to the latest available version.

Step 3 - Migrate the events

Once the update is completed and the Sysdig Monitor application is running, use SSH to login into the server that is hosting your “all-in-one” installation. Store the MySQL server info in the following environment variables:

MYSQL_USER='<INSERT_HERE_THE_MYSQL_USER>'
MYSQL_PWD='<INSERT_HERE_THE_MYSQL_PASSWORD>'

If you have not changed the defaults from when Sysdig Monitor was first installed, the settings will be:

MYSQL_USER='admin'
MYSQL_PWD='password'

While still logged into this host, execute the event migration by running the following container:

docker run --rm -it --net=host sysdig/onprem_migration:events --mysql_endpoint 127.0.0.1 --mysql_user ${MYSQL_USER} --mysql_password ${MYSQL_PWD} --es_url http://127.0.0.1

A sample output of correct events migration:

2017-02-10 16:50:20.259  INFO 7 --- [           main] com.draios.services.MigrationService     : starting events migration.
2017-02-10 16:50:20.284  INFO 7 --- [           main] com.draios.services.MigrationService     : Starting from id 0
2017-02-10 16:50:20.830  INFO 7 --- [           main] com.draios.services.MigrationService     : Indexed 100 events; latest id is 100
2017-02-10 16:50:20.835  INFO 7 --- [           main] com.draios.services.MigrationService     : Avergage duration per batch (run 1 of size 100): 546ms
2017-02-10 16:50:20.843  INFO 7 --- [           main] com.draios.services.MigrationService     : db events: 100
2017-02-10 16:50:20.844  INFO 7 --- [           main] com.draios.services.MigrationService     : no more events to migrate, exiting.

Step 4 - Verify migration of your events

Log in to the Sysdig Monitor application and check that all your events from before the migration are available by navigating to the page Events > Custom Events.

Step 5 - Clean up

Once the migration is completed, perform the following clean-up command to remove the remnants of the migration tool:

docker rmi sysdig/onprem_migration:events
Have more questions? Submit a request