Hitachi

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


[Figure]Windows exporter (Hyper-V monitoring) discovery configuration file (jpc_file_sd_config_windows_hyperv.yml)

Organization of this page

Format

Write in YAML format.

- targets:
  - JP1/IM - Agent-installation-hostname:Windows exporter (Hyper-V monitoring)-port-number
  labels:
    jp1_pc_exporter: JPC Windows exporter hyperv
    jp1_pc_nodelabel: Hyperv metric collector(Windows exporter hyperv)
    jp1_pc_category: VirtualMachine
    jp1_pc_agent_create_flag: false
    jp1_pc_multiple_node: "{__name__=~'windows_hyperv_vm_cpu_total_run_time|windows_hyperv_host_.*'}"

File

jpc_file_sd_config_windows_hyperv.yml

jpc_file_sd_config_windows_hyperv.yml.model (model file)

Storage destination directory

- Integrated agent host

For Windows

  • For physical hosts (definition files and model files)

    Agent-path\conf\

  • Logical host (definition file)

    Shared-folder\jp1ima\conf\

Description

This file is used to set Windows exporter (Hyper-V monitoring) scrape by Prometheus server.

Character code

UTF-8 (without BOM)

Line feed code

CR+LF

Time of import of definitions

When Prometheus server reload API is executed or restarted, Prometheus server is subject to scrape. After that, when you execute jddcreatetree command and jddupdatetree command, it is reflected in the content displayed in integrated operation viewer tree.

Description

JP1/IM - Agent-installation-hostname

Specifies IP address/hostname of scrape destination Windows exporter (Hyper-V monitoring.

Windows exporter (Hyper-V monitoring)-port-number

Specifies the port number of scrape destination Windows exporter (Hyper-V monitoring.

By default, 20733 is specified.