Hitachi

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


[Figure]Promitor discovery configuration file (jpc_file_sd_config_promitor.yml)

Organization of this page

Syntax

Written in YAML format.

- targets:
  - installation-host-name:Promitor-Scraper-port-number
  labels:
    jp1_pc_exporter: JPC Promitor
    jp1_pc_trendname: promitor
    jp1_pc_remote_monitor_instance: installation-host-name:Azure metric collector (Promitor)
jp1_pc_rm_agent_create_flag: false

File

jpc_file_sd_config_promitor.yml

jpc_file_sd_config_promitor.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 Promitor to be scraped by the Prometheus server.

Character encoding

UTF-8 (without BOM)

Linefeed code

In Windows: CR+LF

In Linux: LF

Timing in which definitions are reflected

The Promitor 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:Promitor-Scraper-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 Promitor Scraper port number has changed from its default value, change the Promitor-Scraper-port-number value after the colon (:).