Sample file of Script exporter configuration file for SAP system monitoring (jpc_script_exporter_sap.yml)
- Organization of this page
Format
This example is provided as sample to monitor SAP in the following conditions.
- Conditions
<Common the SAP system log extract commands>
-
The prerequisites described in 3.15.5 SAP system monitoring function in the JP1/Integrated Management 3 - Manager Overview and System Design Guide are met.
-
The path relative to the working folder specified in the Script exporter service definition file, and the environment parameters file is stored in the following folder.
../conf/user/
-
IM management node categories
Enterprise
-
Specify a max_timeout value that is less than the Prometheus server scrape interval. Since the value of the max_timeout is set to 30, change the value of max_timeout if the Prometheus server scrape interval is less than or equal to 30.
<jr3slget command>
-
Output system log information of SAP instance "o246bci_SD5_00".
-
The following information was specified in the environmental parameters file (jr3slget.ini) when the command was executed to extract system log information:
-
RFC access information
-
Target information
-
Log file to which the system log information is output
-
Command working directory
-
-
The timestamp file is stored in the jr3slget folder below the working folder specified in the environment parameters file.
-
Label name of IM management node: SAP Syslog extractor(jr3slget)
<jr3alget command>
-
Specify "SAP CCMS Monitor Templates" for the monitor set name and "Entire System" for the monitor name to print CCMS alert message.
-
The following information is specified in the environment parameters file (jr3alget.ini) when extracting CCMS alert information by executing the command.
-
RFC access information
-
Target information
-
Log file to which CCMS alerting information is output
-
Command working directory
-
-
The timestamp file is stored in the jr3slget folder below the working folder specified in the environment parameters file.
-
Label name of IM management node: SAP CCMS Alert extractor(jr3alget)
- Definition example
scripts: - name: SAP Syslog extractor(jr3slget) command: jr3slget-command-path args: - "-lasttime" - "sltimestamp.txt" - "-x2" - "-cnf" - "../conf/user/jr3slget.ini" timeout: max_timeout: 30 enforced: true - name: SAP CCMS Alert extractor(jr3alget) command: jr3alget-command-path args: - "-lasttime" - "altimestamp.txt" - "-x2" - "-cnf" - "../conf/user/jr3alget.ini" timeout: max_timeout: 30 enforced: true
File
jpc_script_exporter_sap.yml
Storage directory
- Integrated agent host
In Windows:
-
For a physical host
Agent-path\conf\sample\
In Linux:
-
For a physical host
/opt/jp1ima/conf/sample/
Description
This configuration file defines Script exporter operation for SAP system monitoring. Copy the sample file (jpc_script_exporter_sap.yml), change the file name of the destination to "jpc_script_exporter.yml", and place it in the placement destination of the Script exporter configuration file (jpc_script_exporter.yml). For the location of the files, see Appendix A.4(3) Integrated agent host (Windows) and Appendix A.4(4) Integrated agent host (Linux) in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.
Character code
See to the explanation of Character encoding in Script exporter configuration file (jpc_script_exporter.yml).
Line feed code
See the explanation of Line feed code in Script exporter configuration file (jpc_script_exporter.yml).
When the definitions are applied
See the explanation of When the definitions are applied in Script exporter configuration file (jpc_script_exporter.yml).
Information that is specified
See the explanation of Information that is specified in Script exporter configuration file (jpc_script_exporter.yml).
When you define a script in Script exporter configuration file that executes the SAP system log extract command, script.name must include the SAP system log extract command name (jr3slget, or jr3alget) to be executed. Otherwise, an IM management node for the metric output function of SAP system monitoring is created under Other Applications category.
When you create multiple environment parameters file that differ in parameter settings, such as when defining multiple RFC destinations (multiple instance), you define multiple scripts as shown in the following example definition.
scripts: - name: SAP Syslog extractor(jr3slget)_A command: C:/Program Files (x86)/Hitachi/jp1pc/agtm/evtrap/jr3slget.exe args: - "-lasttime" - "sltimestamp_A.txt" - "-x2" - "-cnf" - "../conf/user/jr3slget_A.ini" timeout: max_timeout: 30 enforced: true - name: SAP CCMS Alert extractor(jr3alget)_A command: C:/Program Files (x86)/Hitachi/jp1pc/agtm/evtrap/jr3alget.exe args: - "-lasttime" - "altimestamp_A.txt" - "-x2" - "-cnf" - "../conf/user/jr3alget_A.ini" timeout: max_timeout: 30 enforced: true - name: SAP Syslog extractor(jr3slget)_B command: C:/Program Files (x86)/Hitachi/jp1pc/agtm/evtrap/jr3slget.exe args: - "-lasttime" - "../data/script_exporter/jr3slget/sltimestamp_B.txt" - "-x2" - "-cnf" - "../conf/user/jr3slget_B.ini" timeout: max_timeout: 30 enforced: true - name: SAP CCMS Alert extractor(jr3alget)_B command: C:/Program Files (x86)/Hitachi/jp1pc/agtm/evtrap/jr3alget.exe args: - "-lasttime" - "altimestamp_B.txt" - "-x2" - "-cnf" - "../conf/user/jr3alget_B.ini" timeout: max_timeout: 30 enforced: true