Summary of amendments

The version of Intelligent Integrated Management Database was added to the information that can be output by the argument "-display" of the jimgndbsetup command.

jimgndbsetup

A job monitoring function was added that can detect performance issues by monitoring the transitions in the execution times of JP1/AJS3 root jobnet.

Accordingly, a description for using the job monitoring function was added to the explanation of the evaluation_interval (the evaluation interval for the alert rule) of Prometheus configuration file.

In addition, the name of the root jobnet (the information for getting trend data) was added to the information retrieved from JP1/AJS.

Prometheus configuration file(jpc_prometheus_server.yml), 7.1.4(2)

You changed or added the following parameters to Intelligent Integrated Management Database configuration file (postgresql.conf):

• The following parameter was changed:

  - Settings in JP1/IM - Manager settings for log_min_messages (the level of messages written to the server log)

• The following parameters were added:

  - Logging_collector (Whether or not Intelligent Integrated Management Database log file is output)

  - log_error_verbosity (the level of detail information for each message written to the server log)

  - log_timezone (time zone used for the timestamp written to the server log)

  - log2 (Intelligent Integrated Management Database log file type)

  - log2_rotation_count (the number of sectors of Intelligent Integrated Management Database log file)

  - log2_rotation_max_size (the maximum size of Intelligent Integrated Management Database log file)

Intelligent Integrated Management Database configuration file (postgresql.conf)

Added $stepTime{minSeconds="minimum-seconds"} to dynamically calculate to include all data according to the dashboard trend data display range as a range vector selector that can be specified in promql of metric definition file.

Accordingly, the explanation of the range vector selector was added to the explanation of promql of Node exporter metric definition file (metrics_node_exporter.conf).

In the model file of the following metric definition file, the value of the range vector selector described in promql settings (initial status) was changed from "2m" (fixed value) to "$stepTime{minSeconds=\"120\"}".

• Node exporter metric definition file (metrics_node_exporter.conf)

• Windows exporter metric definition file (metrics_windows_exporter.conf)

• Windows exporter (Hyper-V monitoring) metric definition file for host (metrics_windows_exporter_hyperv_host.conf)

• Windows exporter (Hyper-V monitoring) metric definition file for VM (metrics_windows_exporter_hyperv_vm.conf)

• Node exporter for AIX metric definition file (metrics_node_exporter_aix.conf)

• OracleDB exporter metric definition file (metrics_oracledb_exporter.conf)

• SQL exporter metric definition file (metrics_sql_exporter.conf)

• Container monitoring metric definition file (metrics_kubernetes.conf)

Node exporter metric definition file (metrics_node_exporter.conf), Windows exporter metric definition file (metrics_windows_exporter.conf), Windows exporter (Hyper-V monitoring) metric definition file for host (metrics_windows_exporter_hyperv_host.conf), Windows exporter (Hyper-V monitoring) metric definition file for VM (metrics_windows_exporter_hyperv_vm.conf), Node exporter for AIX metric definition file (metrics_node_exporter_aix.conf), OracleDB exporter metric definition file (metrics_oracledb_exporter.conf), SQL exporter metric definition file (metrics_sql_exporter.conf), Container monitoring metric definition file (metrics_kubernetes.conf)

Added a description of range vector selectors to a note of the scrape_interval (scrape interval) in the Prometheus configuration file.

Prometheus configuration file (jpc_prometheus_server.yml)

In the prometheus command options in the service definition file, changed the maximum daily value that can be specified for --storage.tsdb.retention.time (the retention period of performance data) from 15d to 366d.

Service definition file (jpc_program-name_service.xml)