Hitachi

JP1 Version 13 JP1/Integrated Management 3 - Manager Command, Definition File and API Reference


[Figure]Script exporter discovery configuration file (jpc_file_sd_config_script.yml)

Organization of this page

Syntax

Written in YAML format.

- targets:
  - installation-host-name:Script-exporter-port-number
  labels:
    jpc_pc_exporter: JPC Script exporter
    jpc_pc_trendname: script_exporter
    jp1_pc_multiple_node: "{job='jpc_script.*',jp1_pc_multiple_node=''}"
    jp1_pc_agent_create_flag: false

File

jpc_file_sd_config_script.yml

jpc_file_sd_config_script.yml.model (model file)

Storage directory

For Windows
When using a physical host

Agent-path\conf\

When using a logical host

shared-folder\jp1ima\conf\

For Linux
When using a physical host

/opt/jp1ima/conf/

When using a logical host

shared-directory/jp1ima/conf/

Description

This file configures the Script exporter to be scraped by the Prometheus server.

When Script exporter discovery is specified using the file-based file_sd_config method, specify this file to file_sd_configs in scrape_configs in the Prometheus configuration file (jpc_prometheus_server.yml).

Character encoding

UTF-8 (without BOM)

Linefeed code

In Windows: CR+LF

In Linux: LF

Timing in which definitions are reflected

The Script exporter becomes a target for scraping when executing or restarting the Prometheus server reload API. Following this, definitions are reflected in the contents of the integrated operation viewer tree view when the jddcreatetree command and the jddupdatetree command are executed.

Content description

- installation-host-name:Script-exporter-port-number

The installation-host-name is set based on the installation script for the integrated agent. This can also be specified in FQDN format.

If the Script exporter port number has changed from its default value, change the Script-exporter-port-number value after the colon (:).