Blackbox exporter (HTTP/HTTPS monitoring) discovery configuration file (jpc_file_sd_config_blackbox_http.yml)

Format

Write in YAML format.

- targets:
  - Monitored hostname:IM Management Node Label Name:URL
  ...
  labels:
    jp1_pc_exporter: JPC Blackbox Exporter
    jp1_pc_category: serviceResponse
    jp1_pc_trendname: blackbox_exporter
    jp1_pc_remote_monitor_instance: install-host-name: Synthetic metric collector(Blackbox exporter)

To Page Top

File

jpc_file_sd_config_blackbox_http.yml

jpc_file_sd_config_blackbox_http.yml.model (model file)

file_sd_config_blackbox_module-name-start-with-http.yml (user-created)

To Page Top

Storage directory

■Integrated agent host

In Windows:

• For a physical host

  Agent-path\conf\

• For a logical host

  shared-folder\jp1ima\conf\

In Linux:

• For a physical host

  /opt/jp1ima/conf/

• For a logical host

  shared-directory/jp1ima/conf/

To Page Top

Description

A file that configures the Blackbox exporter that Prometheus server scrapes with HTTP/HTTPS monitoring.

If you have newly defined a module in Process exporter configuration file (jpc_blackbox_exporter.yml) HTTP/HTTPS monitoring, create a discovery configuration file with the following name and copy the model file for this discovery configuration file, depending on the target:

file_sd_config_blackbox_module-name.yml

For details on Blackbox exporter monitoring setup, see 1.21.2(6) Setup of Blackbox exporter in the JP1/Integrated Management 3 - Manager Configuration Guide.

To Page Top

Character code

UTF-8 (without BOM)

To Page Top

Line feed code

In Windows: CR+LF

In Linux: LF

To Page Top

When the definitions are applied

When the Prometheus server reload API is executed or restarted, the Prometheus server is subject to scraping. Then, when the jddcreatetree and jddupdatetree commands are executed, the contents of the tree display in the integrated operations viewer are reflected.

To Page Top

Information that is specified

- Monitored hostname:IM Management Node Label Name:URL

Monitored hostname, IM Management Node Label Name, and URL are separated by a ":" (colon).

The Monitored hostname is a character other than 1 to 255 control characters, and specifies the host name of the web server to be monitored. You can also specify the FQDN format. "localhost" cannot be specified.

The IM Management Node Label Name is a character that does not include 1 to 255 characters ":" (colon) and control characters, and specifies the string to be displayed in the IM Manager label name in the Integrated Operations Viewer. Make sure that the string when encoding the URL cannot exceed 234 bytes (the upper limit is 26 characters when all multibyte characters are used).

A URL is a character other than 1 to 2083 control characters that specifies URL to monitor. You can specify IP address instead of Host name in URL, but if you specify IP address, you cannot Enable validation of the monitored certificate (you cannot false in the insecure_skip_verify of Process exporter configuration file (jpc_blackbox_exporter.yml) tls_config). In addition, the following metric cannot be monitored because "true" is Setup to the insecure_skip_verify of the tls_config of Process exporter configuration file (jpc_blackbox_exporter).

• probe_ssl_last_chain_expiry_timestamp_seconds

To Page Top

Example definition

- targets:
  - hostB: Metric forwarder(Prometheus server) healthy:http://hostB:20713/-/healthy
  - hostB: Alert forwarder(Alertmanager) healthy:http://hostB:20714/-/healthy
  labels:
    jp1_pc_exporter: JPC Blackbox Exporter
    jp1_pc_category: serviceResponse
    jp1_pc_trendname: blackbox_exporter
    jp1_pc_remote_monitor_instance: hostA: Synthetic metric collector(Blackbox exporter)

To Page Top