12.3.2 Data about JP1/IM - Agent

The documents required to investigate problems with JP1/IM - Agent are collected by executing the data collection tool. However, if you have already set up the log extraction command for SAP system, you must collect the required data manually.

Organization of this subsection

(1) For Windows

Integrated agent host data can be collected with the data collection tool (jima_log.bat command).

You can also collect the information of AIX host (if a Node exporter for AIX is placed) by using the jima_log_aix.sh command (data collection tool).

This section describes the information collected by the data collection tool.

For details about how to collect integrated agent host documentation, see 12.4.2(1)(a) Integrated agent host, 12.4.2(1)(b) Integrated agent host on Cluster System, and 12.4.2(1)(c) Integrated agent host in Containers.

For details about how to collect data for AIX host to be monitored, see 12.4.2(1)(f) Monitored AIX hosts (When Node exporter for AIX is deployed).

(a) Integrated agent host

The following data can be collected using Windows data collection tool.

For Windows, the data collection tool does not compress the collected data. If necessary, compress it manually with a compression tool, etc.

In addition, collect the documents related to Configuring silence without starting/stopping.

Table 12‒19: Data to be collected by the data collection tool for Windows (Physical Host)
Type of information	Collected data	File name	Storage destination
Product information	Physical host files to be collected in the tables described in "A.4 (3) integrated agent host (Windows)" in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.		`save-destination-folder\jp1_default\jp1ima\`
System log	File generated by executing the command shown in ^#1	`event_list.txt` `event_info.txt` `event_config_info.txt` `System.txt` `Application.txt` `Security.txt`	`save-destination-folder\jp1_default\syslog\`
OS info	Next file on the host `%systemroot%\system32\drivers\etc\hosts` `%systemroot%\system32\drivers\etc\services`	`hosts` `services`	`save-destination-folder\jp1_default\os\`
OS info	File generated by executing the command shown in #2	`hostname.txt` `Os_system.txt` `getenv.log`	`save-destination-folder\jp1_default\os\`
Communication status	File generated by executing the command shown in #3	`netstat.txt` `firewall.txt`	`save-destination-folder\jp1_default\communication\`
Process information	File generated by executing the command shown in #4	`proc_svc.list` `proc_v.list`	`save-destination-folder\jp1_defaul\t\process\`
Configuring silence	File to be collected in the manner shown in #5	`Scilence.txt` Note: If silence setting contains sensitive information such as passwords, delete the corresponding definition from the definition file after collection.	`save-destination-folder\jp1_default\scilence\`
File list	File generated by running the following command on the host `dir /S` `install-destination`	`jp1ima_list.txt`	`save-destination-folder\jp1_default\list\`
Installation documentation	File generated by running the following command on the host `system-drive\Windows\Temp\HCDINST\`	All files under the folder on the left	`save-destination-folder\jp1_default\inst\`
Secret key	File generated by running the following command on the host `jimasecret -list > secretkeys.txt`	`secretkeys.txt`	`save-destination-folder\jp1_default\secret\`
Service information	File generated by running the following command on the host `sc query > service.list 2>&1`	`service.list`	`save-destination-folder\jp1_default\service\`

#1

The following commands collect data related to the system log.

wevtutil el 2> nul 1> event_list.txt
for /f "delims=" %i in (event_list.txt) do echo %i 2> nul 1>> event_info.txt& wevtutil gli "%i" 2> nul 1>> event_info.txt& echo ----- 2> nul 1>> event_info.txt
wevtutil qe System /rd:true /f:text 2> nul 1> System.evt
wevtutil qe Application /rd:true /f:text 2> nul 1> Application.evt
wevtutil qe Security /rd:true /f:text 2> nul 1> Security.evt
for /f "delims=" %i in (event_list.txt) do echo %i 2> nul 1>> event_config_info.txt& wevtutil gl "%i" 2> nul 1>> event_config_info.txt& echo ----- 2> nul 1>> event_config_info.txt

#2

The following commands are used to collect OS data.

hostname 1> hostname.txt 2>nul
"%CommonProgramFiles%\Microsoft Shared\MSInfo\msinfo32" /report os_system.txt /categories SystemSummary 2>nul 1>nul
set > getenv.log

#3

The following commands are used to collect data related to communication status.

echo --Command netsh interface ip show address -- 1>> netstat.txt 2>nul
netsh interface ip show address 1>> netstat.txt 2>nul
echo --Command netsh interface ipv6 show address -- 1>> netstat.txt 2>nul
netsh interface ipv6 show address 1>> netstat.txt 2>nul
echo -- netsh advfirewall show currentprofile -- 1> firewall.txt 2>nul
netsh advfirewall show currentprofile 1>> firewall.txt 2>nul
echo -- netsh advfirewall firewall show rule -- 1>> firewall.txt 2>nul
netsh advfirewall firewall show rule name=all verbose 1>> firewall.txt 2>nul

#4

The following commands collect documentation related to process information.

tasklist /svc > proc_svc.list 2>&1
tasklist /v > proc_v.list 2>&1

#5

With Alertmanager services running, collect silence settings by executing Alertmanager's silence list acquisition API. For more information about API, see Getting a List of silence in 5.21.3 Alertmanager in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

If you are operating in a clustered system, you can collect the following data for logical hosts by specifying-l option in Windows collection tool.

Table 12‒20: Data to be collected by the data collection tool for Windows (Logical Host)
Type of information	Collected data	File name	Storage destination
Product information	Logical host files that are subject to collection in the tables described in A.4(3) integrated agent host (Windows) in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.		`save-destination-folder\logical-host-name\jp1ima\`
Configuring silence	Files to be collected by the method shown in ^#	`scilence_`logical-host-name`.txt` Note: If silence setting contains sensitive information such as passwords, delete the corresponding definition from the definition file after collection.	`save-destination-folder\logical-host-name\scilence\`
File list	File generated by running the following command on the host `dir/S` `shared-folder` `1>jp1ima_list_logical-host-name.txt 2>nul`	`jp1ima_list`_`logical-host-name.txt`	`save-destination-folder\logical-host-name\list\`
Secret key	File generated by running the following command on the host `jimasecret -list -l` `shared-folder` `> secretkeys.txt`	`secretkeys.txt`	`save-destination-folder\logical-host-name\secret\`

#: With Alertmanager services running, collect silence settings by executing Alertmanager's silence list acquisition API. For details about API, see Getting a List of silence in 5.21.3 Alertmanager in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

(b) Monitored AIX hosts (if Node exporter for AIX are deployed)

The following documents can be collected using the resource collection tool for the monitored AIX.

Table 12‒21: Data collected by the data collection tool for AIX host to be monitored (physical host)
Type of information	Collected data	File name	Storage destination
System log	Next file on the host `/var/adm/syslog/syslog.log` N.B. The destination of the system log is obtained by referring to `/etc/syslog.conf setting`.	`syslog.log`	`jima_log_aix.tar.Z(./_jp1_default/jp1ima/)`
OS info	Next file on the host `/etc/hosts` `/etc/services`	`hosts` `services`	`jima_log.tar.Z` `(./_jp1_default/os/)`
OS info	File generated by executing the command shown in #1	`os_inst_pp.list` `kernel_param.list` `hostname.txt` `os_system.txt` `getenv.log`	`jima_log.tar.Z` `(./_jp1_default/os/)`
`Communication status`	`File generated by executing the command shown in` #2	`netstat.txt` `firewall.txt`	`jima_log.tar.Z` `(./_jp1_default/communication/)`
Process information	File generated by running the following command `Ps -elfa > proc.list 2> /dev/null`	`proc.list`	`jima_log_aix.tar.Z(./_jp1_default/process/)`
File list	File generated by running the following command on the host `ls -lR` `Node-exporter-for-AIX-location/jp1ima > jp1ima_list.txt 2>&1`	`jp1ima_list.txt`	`jima_log_aix.tar.Z(./_jp1_default/list/)`
Auto start/stop setting	Next file on the host `/etc/rc.shutdown`	`rc.shutdown`	`jima_log_aix.tar.Z(./_jp1_default/lsitab/)`
Auto start/stop setting	File generated by running the following command `lsitab -a > lsitab.txt 2> /dev/null`	`lsitab.txt`	`jima_log_aix.tar.Z(./_jp1_default/lsitab/)`

#1

The following commands are used to collect OS data.

echo "-- lslpp -l -a --" > os_inst_pp.list 2> /dev/null
lslpp -l -a >> os_inst_pp.list 2> /dev/null
echo "-- /usr/sbin/instfix -a -icv --" >> os_inst_pp.list 2> /dev/null
/usr/sbin/instfix -a -icv >> os_inst_pp.list 2> /dev/null
lsattr -E -l sys0 > kernel_param.list 2> /dev/null
hostname >> hostname.txt 2> /dev/null
echo "-- uname --" > os_system.txt 2> /dev/null
uname -a >> os_system.txt 2> /dev/null
echo "-- date --" >> os_system.txt 2>&1
date >> os_system.txt 2>&1
env > getenv.log 2> /dev/null

#2

The following commands are used to collect data related to communication status.

echo "--Command netstat -an --" > netstat.txt 2> /dev/null
netstat -an >> netstat.txt 2> /dev/null
echo "--Command netstat -rn --" >> netstat.txt 2> /dev/null
netstat -rn >> netstat.txt 2> /dev/null
echo "--Command ifconfig -a --" >> netstat.txt 2> /dev/null
ifconfig -a >> netstat.txt 2> /dev/null
echo "-- lsfilt --" >> firewall.txt 2>&1
lsfilt >> firewall.txt 2>&1

If you are operating in a clustered system, you can collect the following data for the logical host by specifying -l option in the collection tool for AIX host to be monitored.

Table 12‒22: **Data collected by the data collection tool for AIX host to be monitored (logical host)**
Type of information	Collected data	File name	Storage destination
File list	File generated by running the following command `ls -lR` `logical-host-shared-directory-location/jp1ima > jp1ima_list.txt 2>&1`	`jp1ima_list.txt`	`jima_log_aix.tar.Z(./_jp1_default/list/)`

To Page Top

(2) For UNIX

Integrated agent host data can be collected with the data collection tool (jima_log.sh command).

You can also collect the information of AIX host (if a Node exporter for AIX is placed) by using the jima_log_aix.sh command (data collection tool).

For details about how to collect data for AIX host to be monitored, see 12.4.2(2)(f) AIX host to be monitored (when a Node exporter for AIX is allocated).

(a) Integrated agent host

The following data can be collected using Linux data collection tool.

In addition, collect the documents related to Configuring silence without starting/stopping.

Table 12‒23: Data to be collected by the data collection tool for Linux (Physical Host)
Type of information	Collected data	File name	Storage destination
Product information	Physical host files to be collected in the tables described in A.4(4) integrated agent host (Linux) in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.		`jima_log.tar.gz` `(./jp1_default/jp1ima/)`
System log	Next file on the host `/var/log/messages*`	All files under the folder on the left	`jima_log.tar.gz` `(./jp1_default/syslog/)`
OS info	`Next file on the host` `/etc/hosts` `/etc/services`	`hosts` `services`	`jima_log.tar.gz` `(./jp1_default/os/)`
OS info	`File generated by executing the command shown in` #1	`os_inst_pp.list` `kernel_param.list` `hostname.txt` `os_system.txt` `getenv.log`	`jima_log.tar.gz` `(./jp1_default/os/)`
Communication status	`File generated by executing the command shown in`#2	`netstat.txt` `firewall.txt`	`jima_log.tar.gz` `(./jp1_default/communication/)`
`Process information`	`File generated by executing the command shown in`#3	`proc.list`	`jima_log.tar.gz` `(./jp1_default/process/)`
`Configuring silence`	`File to be collected in the manner shown in` #4	`scilence.txt` Note: `If silence setting contains sensitive information such as passwords, delete the corresponding definition from the definition file after collection.`	`jima_log.tar.gz` `(./jp1_default/scilence/)`
`File list`	`File generated by running the following command on the host` `ls -lR /opt/jp1ima` `ls -l /usr/lib/systemd/system/jpc` `getfacl -R /opt/jp1ima` `getfacl /usr/lib/systemd/system/jpc`	`File on the left`	`jima_log.tar.gz` `(./jp1_default/list/)`
`Installation documentation`	`File generated by running the following command on the host` `/etc/.hitachi/pplistd/pplistd` `/etc/.hitachi/.install.log` `/etc/.hitachi/.uninstall.log` `/tmp/HITACHI_JP1_INST_LOG/Files` below `/etc/.hitachi/bin/SHOWPP`	`File on the left`	`jima_log.tar.gz` `(./jp1_default/inst/)`
`Secret key`	`File generated by running the following command on the host` `jimasecret -list > secretkeys.txt`	`Secretkeys.txt`	`jima_log.tar.gz` `(./jp1_default/secret/)`
`Service information`	`File generated by running the following command on the host` `systemctl list-unit-files -t service > service.list 2> /dev/null`	`Service.list`	`jima_log.tar.gz` `(./jp1_default/service/)`
`Container information`	`Docker,Podman to be collected in the manner shown in`#5	`File on the left`	`jima_log.tar.gz` `(./jp1_default/container/)`
`Auto start/stop setting`	`File generated by executing the command shown in` #6	`unit-definition-file-name.txt`	`jima_log.tar.gz` `(./jp1_default/auto/)`

#1

The following commands are used to collect OS data.

/bin/rpm -qa > os_inst_pp.list 2> /dev/null
/sbin/sysctl -a > kernel_param.list 2> /dev/null
hostname >> hostname.txt 2> /dev/null
echo "-- uname --" > os_system.txt 2> /dev/null
uname -a >> os_system.txt 2> /dev/null
echo "-- ls -l /boot --" >> os_system.txt 2> /dev/null
ls -l /boot >> os_system.txt 2> /dev/null
echo "-- cat /etc/os-release --" >> os_system.txt 2> /dev/null
cat /etc/os-release >> os_system.txt 2> /dev/null
echo "-- timedatectl --" >> os_system.txt 2>&1
timedatectl >> os_system.txt 2>&1
env > getenv.log 2> /dev/null

#2

The following commands are used to collect data related to communication status.

echo "--Command ss -a --" > netstat.txt 2> /dev/null
ss -a >> netstat.txt 2> /dev/null
echo "--Command ip route --" >> netstat.txt 2> /dev/null
ip route >> netstat.txt 2> /dev/null
echo "--Command ip addr --" >> netstat.txt 2> /dev/null
ip addr >> netstat.txt 2> /dev/null
echo "-- iptables -v -n -L --line-numbers --" >> firewall.txt 2>&1
iptables -v -n -L --line-numbers >> firewall.txt 2>&1
echo "-- firewall-cmd --list-all-zones --" >> firewall.txt 2>&1
firewall-cmd --list-all-zones >> firewall.txt 2>&1

#3

The following commands collect documentation related to process information.

ps -elfa > proc.list 2> /dev/null

#4

With Alertmanager services running, collect silence settings by executing Alertmanager's silence list acquisition API. For details about API, see Getting a List of silence in 5.21.3 Alertmanager in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

#5

The following commands collect documents related to container information.

# Docker Information
docker version > . /Docker_Verison 2>&1
docker ps -a --no-trunc > . /Docker_Process_Container_List 2>&1
docker_container_list=`docker ps -a --no-trunc -q`
for loop in $docker_container_list
do
    echo $loop >> Docker_Top 2>&1
    docker top $loop >> Docker_Top 2>&1
    echo $loop >> Docker_Inspect 2>&1
    docker inspect $loop >> Docker_Inspect 2>&1
done
/bin/cat /etc/docker/daemon.json > docker_daemon.json 2>&1
/bin/cat /etc/sysconfig/docker > sysconfig_docker 2>&1
 
# Podman Information
podman version > Podman_Verison 2>&1
podman ps --all --no-trunc --format={{.ID}} > p_Process_Container_List 2>&1
p_container_list=`podman ps --all --no-trunc --format={{.ID}}`
for loop in $podman_container_list
do
    echo $loop >> Podman_Top 2>&1
    podman top $loop hpid args >> Podman_Top 2>&1
    echo $loop >> Podman_Inspect 2>&1
    podman inspect $loop >> Podman_Inspect 2>&1
done

#6

The following commands are used to collect data related to the automatic start/stop setting. Run this command for each unit definition file in JP1/IM - Agent.

systemctl is-enabled unit-definition-file-name > unit-definition-file-name.txt 2> /dev/null

If you are operating in a clustered system, you can collect the following data for logical hosts by specifying-l option in Linux collection tool.

Table 12‒24: Data to be collected by the data collection tool for Linux (Logical Host)
Type of information	Collected data	File name	Storage destination
Product information	Logical host files to be collected in the tables described in A.4(4) integrated agent host (Linux) in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.		`logical-hostname.tar.gz` `(./logical-host-name/jp1ima/)`
Configuring silence	Files to be collected by the method shown in ^#	`scilence`_`logical-host-name.txt` Note: If silence setting contains sensitive information such as passwords, delete the corresponding definition from the definition file after collection.	`logical-host-name.tar.gz` `(./logical-host-name/scilence/)`
File list	File generated by running the following command on the host `dir /S` `shared-directory` `1>jp1ima_list_logical-host-name.txt 2>nul`	`jp1ima_list_logical-host-name.txt`	`logical-host-name.tar.gz` `(./logical-host-name/list/)`
Secret key	File generated by running the following command on the host `jimasecret-list` `shared-directory` `> secretkeys.txt`	`secretkeys.txt`	`logical-host-name.tar.gz` `(./logical-host-name/secret/)`

#: With Alertmanager services running, collect silence settings by executing Alertmanager's silence list acquisition API. For details about API, see Getting a List of silence in 5.21.3 Alertmanager in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

(b) Monitored AIX hosts (if Node exporter for AIX are deployed)

This is the same as 12.3.2(1)(b) Monitored AIX hosts (if Node exporter for AIX are deployed).

To Page Top