What Do I Do If an Error Is Reported When the Logstach on ECS Pushes Data to CSS?

Issue

After Logstash is deployed on an ECS, an error is reported when data is pushed to CSS.

Symptom

After Logstash is deployed on an ECS, an error is reported when data is pushed to CSS. The error message is as follows:

LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError: Got response code '500' contacting Elasticsearch at URL 'https://192.168.xx.xx:9200/_xpack'.

Possible Causes

CSS currently does not integrate the x-pack plugin. When you access CSS after deploying Logstash, the system will check whether x-pack is enabled for CSS.

Procedure

1. Delete the x-pack directory in Logstash.
2. Add the configuration item ilm_enabled => false to elasticsearch under the output tag in the Logstash configuration file.
3. Push data to CSS again.