L.1 Changes in version 13-50

(1) Changes in the manuals 3021-3-L02-40(E), 3021-3-L03-40(E), 3021-3-L04-40(E), 3021-3-L05-40(E), 3021-3-L06-40(E), and 3021-3-L07-40(E)

• The following notes or explanations were added to the items specified when acquiring trend data in PromQL.

  • Precaution for labels

  • Description of replacing the backdated timestamp

• The following function was added to the functions available in PromQL, which returns the latest data for each range of time series data.

  • last_over_time

• 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, settings to be applied when upgrading JP1/IM - Manager from version 13-00 to 13-11 to version 13-50 or later have been added.

• 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, the following explanations were added.

  • Script exporter to collect performance data for job information of JP1/AJS3

  • Monitored target name when Windows exporter monitors the Script exporter service (jpc_script_exporter_service) that collects the performance data of the job information of JP1/AJS3

  Also, 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.

• Added notes for upgrading JP1/IM - Manager from version 13-00 to 13-11 to version 13-50 or later.

• Added a description of how to use the jimgndbsetup command to check the version of the Intelligent Integrated Management Database and a description of the version of the Intelligent Integrated Management Database for whichi you must be run the jimgndbupdate command.

• When JP1/IM - Manager 13-50 or later is newly installed, the file name of the log file to be output by the Intelligent Integrated Management Database is set to "postgresql-rotate.log.serial-number-of-sectors", and the number of sectors and the size to be rotated can be set.

  Accordingly, the explanation about the log file output by the Intelligent Integrated Management Database was changed.

• Added explanation of what happens and how to recover from incorrect RemoteWrite configuration when monitoring containers using user-defined Prometheus.

• Added an explanation of range vector selector value specified in PromQL expression in the metric definition file for how to deal with trouble.

• Added factors and measures when the dashboard is slow to be displayed or when the batch download of panel data is slow.

• Added a description of panel operations displayed on the dashboard being edited.

  In addition, Time difference from the dashboard display range (start time or end time) was added to Specification method in Display range setting that can be set for each panel.

• Added an explanation about the conditions that cause the dashboard panel to take a long time to load.

• The range of values that can be specified for the number of plots in the Trend panel has been changed.

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

• 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)

• 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)

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

• 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.

• The following message was changed.

  KNAN12094-I

• The following messages were added.

  • KNAN12160-E, KNAN12161-W, KAJY04206-E, KAJY04207-E, KAJY12016-I, KAJY24205-E, KAJY24206-W

To Page Top