No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

eSight V300R009C00 Local HA System Software Installation Guide (SUSE Linux + MySQL + OMMHA) 10

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
(Optional) Connecting the ELK Server to eSight

(Optional) Connecting the ELK Server to eSight

This section describes how to configure the connection between eSight and the ELK server. Run logs of eSight can be forwarded to the ELK server.

Prerequisites

  • The ELK server has been deployed by the ELK integrator.
  • The ELK integrator has deployed the ELK client Logstash on the active and standby eSight servers. The installation path, IP address, and used port number of Logstash do not conflict with those of eSight. For the Logstash, the disk space usage does not exceed 600 MB and the memory space usage does not exceed 500 MB.
    NOTE:

    For details about ports used by eSight, see the eSight Communication Matrix.

    Perform the following steps to obtain eSight VxxxRxxxCxx Communication Matrix:

    1. Log in to the Huawei technical support website.
    2. Enter the keyword eSight VxxxRxxxCxx Communication Matrix, and click Search.

      Replace VxxxRxxxCxx with the actual version number.

    3. Download eSight VxxxRxxxCxx Communication Matrix in the search result.

Procedure

  1. Log in to the active eSight server as the root user.
  2. Configure the patch for the Logstash to receive run logs of eSight. The Logstash-2.4.0 is used as an example.

    1. Open the elk_input.conf file.

      cd /opt/logstash/logstash-2.4.0/config/logstash-shipper

      NOTE:

      In the command, /opt/logstash/logstash-2.4.0 is the installation directory of the Logstash. Change it based on the site requirements.

      vi elk_input.conf

    2. Press I to enter the editing mode.
    3. Set path to the run log path of eSight.
      input {
          file {
              type => "messages"
              path => [
                  "/opt/eSight/AppBase/var/iemp/log/root.log"
              ]
              sincedb_write_interval => 15
          }
          heartbeat{
              interval => 10
              type => "heartbeat"
          }
      }

      In the information, /opt/eSight/ indicates the eSight installation directory. Change it based on the site requirements.

      At least the key log file root.log is collected. Other log files can also be collected.

    4. Press Esc to exit the editing mode, and run the :wq command to save and exit the file.
    5. Run the following command to restart the ELK agent.

      sh /opt/logstash/logstash-2.4.0/bin/stop_shipper.sh

      sh /opt/logstash/logstash-2.4.0/bin/start_shipper.sh

      NOTE:

      In the command, /opt/logstash/logstash-2.4.0 is the installation directory of the Logstash. Change it based on the site requirements.

  3. Log in to the standby eSight server as the root user and perform 2.
  4. Log in to the ELK server and check whether the ELK receives run logs of eSight.
Download
Updated: 2019-09-02

Document ID: EDOC1100011856

Views: 91141

Downloads: 53

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next