Starting a Logstash Migration Task

Scenario

1. Test the network connectivity between the data source and destination and the Logstash cluster. For details, see Testing Connectivity.
2. Start a Logstash migration task by starting a configuration file.
   • If there is no Running task in the pipeline list, go to Starting a Configuration File.
   • If there is a Running task, go to Hot Starting a Configuration File.
3. Monitor the migration task through metrics, operation records, and run logs. For details, see Monitoring Migration Tasks.

Constraints

• There can be up to 50 Running configuration files in the pipeline list of a Logstash cluster.
• Configuration files that use the logstash stdin plugin cannot use the Hot Start option.
• If hot-starting a configuration file fails and the Logstash process exits unexpectedly, the cluster will try to restart the original Logstash process. Exercise caution when using the Hot Start option.

Testing Connectivity

1. Go to the Configuration Center page.
   1. Log in to the CSS management console.
   2. In the navigation pane on the left, choose Clusters > Logstash.
   3. In the cluster list, click the name of the target cluster. The cluster information page is displayed.
   4. Click the Configuration Center tab.
2. On the Configuration Center page, click Test Connectivity.
3. In the Test Connectivity dialog box, enter the IP address and port number of the data source and destination, and click Test.

   You can test a maximum of 10 IP addresses at a time. You can click Add to add more IP addresses and click Test at the bottom to test connectivity to multiple IP addresses at a time.

   If Available is displayed, the network is connected. If the network is disconnected, configure routes for the Logstash cluster to connect the clusters. For details, see .

Starting a Configuration File

1. In the configuration file list, select configuration files you want to start, and click Start in the upper left corner.
2. In the Start Logstash dialog box, select Keepalive if necessary.

   When Keepalive is enabled, a daemon process will be configured on each node. If the Logstash service becomes faulty, the daemon process will try to rectify the fault and restart the service. You are advised to enable Keepalive for services running long-term. Do not enable it for services running only short-term, or your migration tasks may fail due to a lack of source data.

3. Click OK to start the configuration file and hence the Logstash migration task.

   You can view the started configuration file in the pipeline list.

Hot Starting a Configuration File

1. In the configuration file list, select a configuration file, and click Hot Start in the upper left corner.
2. In the Hot Start Logstash Configuration dialog box, the Keepalived setting is kept consistent with other tasks in the pipeline list by default and cannot be changed.
3. Click OK to hot-start the configuration file and hence the Logstash migration task.

   You can view the hot-started configuration file in the pipeline list.

Monitoring Migration Tasks

• In the pipeline list, click Metric Monitoring in the Operation column to go to the Cloud Eye console and view monitoring information.

  When the Events data of a pipeline changes dynamically, the monitoring data changes accordingly. When a pipeline task is being started or stopped, or the Events data is stable, the monitoring data remains unchanged.

  For details about the monitoring metrics supported, see Logstash Pipeline Monitoring Metrics. For how to configure monitoring alarms, see Using Cloud Eye to Monitor Logstash Clusters.

• You can also click View Operation Record or View Running Log above the pipeline list to view configuration file operation records or the run logs of a migration task.