Preparing to collect logs by enabling BMC Helix logging

BMC Helix Logging uses Elasticsearch, Fluent Bit, and Kibana (EFK) to collect, store, and view logs:

  • Elasticsearch: A search engine also used to store and analyze logs.
  • Fluent Bit: Aggregates the application logs collected by the log shipper and sends them to Elasticsearch.
  • Kibana: A web user interface for data visualization and a log exploration tool.

As a system administrator, you must deploy and configure BMC Helix Logging to collect logs, and then configure the Kibana to view logs. 

Important

BMC Helix Continuous Optimization does not support BMC Helix Logging.

Before you begin

  • BMC Helix IT Operations Management version 23.4.00 must be installed.
  • Make sure that the following ports are available for Elasticsearch and Kibana services: 

    ServicePortsCommand to obtain details
    ElasticSearch  9200, 9300
    kubectl -n bmc-helix-logging get svc | grep elastic


    Kibana5601
    kubectl -n bmc-helix-logging get svc | grep kibana

    Important

    The traffic to Kibana ports is routed from the Load balancer on port 443 to the Ingress controller. As the Ingress controller decides the internal routing of the traffic, the Kibana ports should be open in the Kubernetes cluster.

To prepare to collect logs by enabling BMC Helix Logging

  1. In the helix-on-prem-deployment-manager-<release_version>/ configs /deployment.config file, change the value of the BMC_HELIX_LOGGING parameter to yes:
    BMC_HELIX_LOGGING=yes

    Important

    If the value of the BMC_HELIX_LOGGING parameter is no, the BMC Helix IT Operations Management supportability is limited, and the root cause analysis of an issue might not be possible.

  2. Go to helix-on-prem-deployment-manager/configs/bmc-helix-logging.config and set the following values:

    • To use IPv4, set ESKIBANA_SERVER_HOST="0.0.0.0"
    • To use IPv6, set ESKIBANA_SERVER_HOST="::"


Was this page helpful? Yes No Submitting... Thank you

Comments