Collecting logs and activating traces

Log files for HERO components are located inside the respective containers.

In case of issues, it is recommended to check the status of the containers. Run the following command:

docker ps -a

If you find containers that are in a non-running or restarting status, download the respective log files.

The list of HERO containers follows:

 

HERO Container

  Description

keycloak

HERO security server. It manages all the user logins and info

keycloak-db

Keycloak container database

hero-elasticsearch

noSQL database for KPIs, prediction data, and runbook information

hero-kibana

Dashboard visual service: displays charts with actual and estimated KPIs

hero-tomcat

Tomcat server that runs HERO war files and exposes the Web UI

hero-prediction

Container managing KPIs prediction, based on a Python process

hero-nginx

HERO reverse-proxy container, managing all the external connections to HERO

 

To extract all the available log files from a container, run the command:

docker logs [container_name]

For additional details and options, see Docker documentation.

 

Usually, the log files extracted from each container will be sufficient to troubleshoot the component issues.

For hero-prediction container, for a more detailed problem determination you can run the additional command:

docker exec hero-prediction cat out_WA.txt  (you can run this command only if the container is running)

 

To download the log files from containers, see Docker documentation.

 

To activate HERO traces, run the following steps:

  1. From the directory where HERO has been installed, type docker ps

  2. Identify the Tomcat container hero-tomcat and type docker exec -it hero-tomcat bash

  3. Run the following command: apt-get install vim

  4. Go to /deployments/apache-tomcat/webapps/Dashboard/WEB-INF/classes  folder  and open log4j.properties file

  5. If you want to change from DEBUG level to TRACE level, uncomment  log4j.logger.com.hcl=DEBUG removing the #, and write TRACE instead of DEBUG

  6. From the directory where HERO has been installed, type docker restart hero-tomcat

 

Leave feedback