Windows exporter (process monitoring) metric definition file (metrics_windows_exporter_process.conf)

Syntax

The same as the JP1/IM - Agent Windows exporter metric definition file.

To Page Top

File

metrics_windows_exporter_process.conf

metrics_windows_exporter_process.conf.model (Model file)

To Page Top

Storage directory

For Windows

When using a physical host

Manager-path\conf\imdd\plugin\jp1pccs\

When using a logical host

shared-folder\jp1imm\conf\imdd\plugin\jp1pccs\

For Linux

When using a physical host

/etc/opt/jp1imm/conf/imdd/plugin/jp1pccs/

When using a logical host

shared-directory/jp1imm/conf/imdd/plugin/jp1pccs/

To Page Top

Description

This file defines Windows exporter (process monitoring) metric information shown in the Trends tab of the Integrated Operation Viewer window.

Definitions are used for the return values of the __metricListGet method and __timeSeriesDataGet method for JP1/IM - Agent product plug-ins. If JP1/IM - Manager is in a hierarchical configuration and trend data stored in the database of a lower-level manager is referenced from an upper-level manager, you must add the metrics of the referenced trend data to the metrics definition file of the upper-level manager.

To Page Top

Character encoding

UTF-8 (without BOM)

To Page Top

Linefeed code

In Windows: CR+LF

In Linux: LF

To Page Top

Timing in which definitions are reflected

The same as the JP1/IM - Agent Windows exporter metric definition file.

To Page Top

Content description

The same as the JP1/IM - Agent Windows exporter metric definition file.

To Page Top

Settings in the model file (initial status) and examples of alert definitions

The following shows the settings (initial status) of each metric written in the Windows exporter (process monitoring) metric definition file (model file), and examples of alert definitions (alert configuration file).

• process_pgm_process_count^#

  - Settings (initial status)

  Member		Setting (initial status)
  name		process_pgm_process_count
  default		true
  promql for the metric definition file (including $jp1im_TrendData_labels)		count by (instance, job, jp1_pc_nodelabel, jp1_pc_prome_hostname) (windows_process_start_time and $jp1im_TrendData_labels)
  resource_en	category	platform_windows_process
  	label	Process count
  	description	Number of processes that are executing programs. Number of processes that have this program name inside the process table. [Units: count]
  	unit	count

  #

  This has no equivalent field in JP1/PFM - Agent for Platform (Windows). This is equivalent to the PROCESS_COUNT field (addition for alive monitoring) in the JP1/PFM - Agent for Platform (UNIX) PD_PGM record.

  - Examples of alert definitions^#

  groups:
   - name: windows_exporter
    rules:
     - alert: process_pgm_process_count(Windows exporter)
       expr: absent(windows_process_start_time{instance="integrated-agent-host-name:Windows-exporter-port-number", job="jpc_windows", jp1_pc_exporter="JPC Windows exporter", jp1_pc_nodelabel="monitored-process-name",process="monitored-process-name"}) == 1
        for: 3m
        labels:
          jp1_pc_product_name: "/HITACHI/JP1/JPCCS2"
          jp1_pc_severity: "Error"
          jp1_pc_eventid: "0414"
          jp1_pc_metricname: "windows_process_start_time"
        annotations:
          jp1_pc_firing_description: "The number of processes has fallen below the threshold (1 process)."
          jp1_pc_resolved_description: "The number of processes has exceeded the threshold (1 process)."

  #

  This uses a threshold value of 1 as an example. Change this value based on the number of monitoring targets.

  When defining multiple alerts with the same integrated agent host, avoid specifying duplicate groups:, or specifying a name that specifies the same group name in duplicate.

To Page Top