Problem

Core Services are embedded within containers and Support are requested logs or configuration files from these containers to work on Support cases. It could be a pain for customers and Support that can waste time in collecting only part of expected logs or the wrong ones.

Resolution

To be more efficient and speed up Support case processing, project team developed a small tool to assist our customers for this task.

Minimum Update for Core Services: Update 4

The process below show you how to deploy the solution and how to use it:

• Create a folder where to put the attached file

$ mkdir collect_logs

$ pwd

/my_Automator_CS/automator-services/collect_logs

• Uncompress the attached file into the created folder
  

$ ls -l

-rw-rw-r-- 1 root root 42 Mar 26 16:43 configcs.ini

-rwxrwxr-x 1 root root 9200 Mer 28 12:47 cs_logs.bash

• Set up the configuration file configcs.ini with the path of automator-services (config directory)
• Run ./cs_logs.bash -h to view the different options for this tool
• Launch the command ./cs_logs.bash ACT to activate the log collection tool

$ ./cs_logs.bash ACT

CS version = 4.1.5.51
Script compatible with the version of CS used

Core Services data in /coreservices/data-services
Location of log files for the different containers : /coreservices/data-services/logs

Log activation for core services containers
Activation document-manager log in /supervision-data/document-manager/config/logback-spring.xml file
Activation itopsvision-automator log in /supervision-data/itopsvision-automator/config/logback-spring.xml file
Activation itopsvision-automator-aggregation log in /supervision-data/itopsvision-automator-aggregation/config/logback-spring.xml file
Activation itopsvision-ui log in /supervision-data/itopsvision-ui/config/logback-spring.xml file


• Once the problem is reproduced after activating the logs, use the command ./cs_logs.bash LOG to collect the logs and configuration file into the zipped file log_containers.tar.gz (File to send/attach to your support core services open case)

$ ./cs_logs.bash LOG
CS version = 4.1.5.51
Script compatible with the version of CS used

Core Services data in /supervision-data
Location of log files for the different containers : /supervision-data/logs

Containers logs collection for Axway support; file log_containers.tar.gz will be created in current directory

$ ls
configcs.ini cs_logs.bash log_containers.tar.gz

Notice: you can stop the logs collection by using the command ./cs_logs.bash DES