The connection between the Filebeat service and Centralized Logging Service failed.
Cause
The Filebeat service continuously sends the logs from the configured log locations to Centralized Logging Service.
If the connection between the Filebeat service and Central Logging Service fails, the system records a connection failure error in the filebeat.log file. The probable causes of connection errors can be physical connection failures, TLS connection failures, or incorrect configurations in the filebeat.yml file.
The system raises the FILEBEATCONNECTIONERROR alarm when it detects a Filebeat service connection failure.
Solution
Procedure
Check the Filebeat log to determine the cause of the connection failure.
The Filebeat log is located at /var/log/Avaya/filebeat/filebeat.log on the Avaya Breeze® platform server.
Check the physical connection between the Filebeat service cluster and the Centralized Logging Service cluster.
The physical connection failure can occur when the destination host is restarted or shut down.
Check the connection between the Filebeat service cluster and the Centralized Logging Service cluster.
If both the source host and the destination host are configured for secure communication, a secure TLS connection is established.
If both the source host and the destination host are similarly not configured for secure communication, an insecure connection is established.
If the source host and the destination host have different configurations, a connection is not established.
The Filebeat service tries to connect to the logstash destination at /etc/filebeat/filebeat.yml.
Check the Websphere certificate configuration of the destination host.
For secure communication, the Websphere certificate must have the management IP added as Subject Alternative Name (SAN).
