Hitachi

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


Service definition file (jpc_program-name_service.xml)

Organization of this page

Format

<service>
  <id>service-ID</id>
  <name>display-name-of-the-service</name>
  <description>description</description>
  <workingdirectory>working-directory</workingdirectory>
  <env name="environment-variable-name" value="value"></env>
  <executable>"program-path"</executable>
  <arguments>arguments-of-the-program</arguments>
  <startmode>type-of-startup</startmode>
  <logpath>log-output-directory</logpath>
  <log mode="roll-by-size">
    <sizeThreshold>log-file-size</sizeThreshold>
    <keepFiles>Number of log faces</keepFiles>
  </log>
  <stoptimeout>Termination timeout period</stoptimeout>
</service>

File

Storage directory

■Integrated agent host
  • For a physical host (Model File storage destination)

    Agent-path\conf\

  • For Physical host and Logical host (storage destination of definition file)

    Agent-path\bin\

Description

This is the definition file of the Windows serviced program.

Character code

UTF-8 (without BOM)

Line feed code

CR+LF

When the definitions are applied

If you change <startmode> in the definition file, it will take effect by reinstalling the service. For each JP1/IM agent control base or add-on program service, reinstall the service using the commands listed in the following tables.

Add-on program or JP1/IM agent control base

Service name

Command

Prometheus server

jpc_prometheus_server_service.exe

jpc_prometheus_server_service.exe

Alertmanager

jpc_alertmanager_service.exe

jpc_alertmanager_service.exe

Windows exporter

jpc_windows_exporter_service.exe

jpc_windows_exporter_service.exe

Blackbox exporter

jpc_blackbox_exporter_service.exe

jpc_blackbox_exporter_service.exe

Yet another cloudwatch exporter

jpc_ya_cloudwatch_exporter_service.exe

jpc_ya_cloudwatch_exporter_service.exe

Promitor

jpc_promitor_scraper_service.exe

jpc_promitor_scraper_service.exe

jpc_promitor_resource_discovery_service.exe

jpc_promitor_resource_discovery_service.exe

Script exporter

jpc_script_exporter_service.exe

jpc_script_exporter_service.exe

Fluentd

jpc_fluentd_service.exe

jpc_fluentd_service.exe

imagent

jpc_imagent_service.exe

jpc_imagent_service.exe

imagentproxy

jpc_imagentproxy_service.exe

jpc_imagentproxy_service.exe

imagentaction

jpc_imagentaction_service.exe

jpc_imagentaction_service.exe

If you change the <arguments> or <stoptimeout> of File, it is reflected by Restart of theservice.

Information that is specified

Item

Description

Changeability

What You Setup in Your JP1/IM - Agent

JP1/IM - Agent Defaults Value

<service>

Configure the service settings.

--

--

--

<id>

Specify the ID of the service (the ID that Windows uses internally to identify the service) (required).

This identifier must be unique among all services installed on the system and must consist entirely of alphanumeric characters.

N

--

  • For Prometheus server

    jpc_prometheus

  • For Alertmanager

    jpc_alertmanager

  • For Windows exporter

    jpc_windows_exporter

  • For Blackbox exporter

    jpc_blackbox_exporter

  • For JP1/IM agent control base (imagent)

    jpc_imagent

  • For JP1/IM agent control base (imagentproxy)

    jpc_imagentproxy

  • For JP1/IM agent control base (imagentaction)

    jpc_imagentaction

  • For Fluentd

    jpc_fluentd

  • For Yet another cloudwatch exporter:

    jpc_ya_cloudwatch_exporter

  • For Promitor Scraper:

    jpc_promitor_scraper

  • For Promitor Resource Discovery:

    jpc_promitor_resource_discovery

  • For Script exporter:

    jpc_script_exporter

  • For OracleDB exporter

    oracledb_exporter_instance name

<name>

Specify a display name for the service (the short display name of the service) (optional).

It can contain spaces and other characters. Do not specify a long string, such as <id>. It must also be unique among all services in a particular system.

N

--

  • For Prometheus server

    JP1/IM3-Agent Metric forwarder

  • For Alertmanager

    JP1/IM3-Agent Alert forwarder

  • For Windows exporter

    JP1/IM3-Agent Windows metric collector

  • For Blackbox exporter

    JP1/IM3-Agent Synthetic metric collector

  • For JP1/IM agent management base (imbase)

    ■For normal hosts

    JP1/IM-Agent Base Server

    ■For cluster environments

    JP1/IM-Agent Base Server_ Name. Logical host

  • For JP1/IM agent management base (imbaseproxy)

    ■For normal hosts

    JP1/IM-Agent Base Proxy Server

    ■For cluster environments

    JP1/IM-Agent Base Proxy Server_ Name. Logical host

  • For JP1/IM agent control base (imagent)

    JP1/IM3-Agent

  • For JP1/IM agent control base (imagentproxy)

    JP1/IM3-Agent proxy

  • For JP1/IM agent control base (imagentaction)

    JP1/IM3-Agent action

  • For Fluentd

    JP1/IM3-Agent Log trapper

  • For Yet another cloudwatch exporter:

    JPC YA Cloudwatch exporter

  • For Promitor Scraper:

    JPC Promitor Scraper

  • For Promitor Resource Discovery:

    JPC Promitor Resource Discovery

  • For Script exporter:

    JPC Script exporter

  • For OracleDB exporter

    OracleDB metric collector instance name

<description>

Specify a description (long description) (optional).

This description is displayed in the Windows Service Control Manager when the service is selected.

N

--

  • For Prometheus server

    Prometheus server

  • For Alertmanager

    Alertmanager

  • For Windows exporter

    windows_exporter

  • For Blackbox exporter

    blackbox_exporter

  • For JP1/IM agent management base (imbase)

    JP1 IMA Base Service

  • For JP1/IM agent management base (imbaseproxy)

    JP1 IMA Base Proxy Service

  • For JP1/IM agent control base (imagent)

    JPC IM-Agent Service

  • For JP1/IM agent control base (imagentproxy)

    JPC IM-Agent Proxy Service

  • For JP1/IM agent control base (imagentaction)

    JPC IM-Agent Action Service

  • For Fluentd

    Fluentd

  • For Yet another cloudwatch exporter:

    jpc_ya_cloudwatch_exporter

  • For Promitor Scraper:

    jpc_promitor_scraper

  • For Promitor Resource Discovery:

    jpc_promitor_resource_discovery

  • For Script exporter:

    jpc_script_exporter

  • For OracleDB exporter

    OracleDB exporter

<workingdirectory>

Specify the working directory (the current directory of the service).

N

--

  • For Prometheus server,Alertmanager,Windows exporter, and Blackbox exporter

    Automatically Setup during set-up.

  • For JP1/IM agent management base (imbase and imbaseproxy)

    Manager-path\bin\imdd\imagent

  • For JP1/IM agent control base (imagent,imagentproxy, and imagentaction) and Fluentd

    Agent-path\bin

<env name="environment-variable-name" value="value">

Specifies the environment-variable-name and its value.

This is specified for Promitor Scraper, Promitor Resource Discovery, and OracleDB exporter.

  • For Promitor Scraper and Promitor Resource Discovery

    N

  • For OracleDB exporter

    Y

--

  • For Promitor Scraper:

    name="PROMITOR_CONFIG_FOLDER"

    value="installation-directory/jp1ima/conf/promitor/scraper"

  • For Promitor Resource Discovery:

    name="PROMITOR_CONFIG_FOLDER"

    value="installation-directory/jp1ima/conf/promitor/resource-discovery"

  • For OracleDB exporter

    See the Preparing to add a monitoring target in 1.23.1(4)(a) Adding a monitoring target (Required) in the JP1/Integrated Management 3 - Manager Configuration Guide.

<executable>

Specify the path of the program (the path of the executable file to be launched) (required).

You can specify an absolute path or specify the executable file name to search from PATH.

Note, however, that services often run under different user accounts, so they may have a different PATH than the shell.

Note that specifying an empty string does not result in an error.

N

--

  • For Prometheus server

    prometheus.exe

  • For Alertmanager

    alertmanager.exe

  • For Windows exporter

    windows_exporter.exe

  • For Blackbox exporter

    blackbox_exporter.exe

  • For JP1/IM agent management base (imbase)

    imbase

  • For JP1/IM agent management base (imbaseproxy)

    imbaseproxy

  • For JP1/IM agent control base (imagent)

    imagent

  • For JP1/IM agent control base (imagentproxy)

    imagentproxy

  • For JP1/IM agent control base (imagentaction)

    Imagentaction

  • For Fluentd

    Agent-path\lib\ruby\ruby.exe

  • For Yet another cloudwatch exporter:

    ya_cloudwatch_exporter.exe

  • For Promitor Scraper:

    promitor_scraper.exe

  • For Promitor Resource Discovery:

    promitor_resource_discovery.exe

  • For Script exporter:

    script_exporter.exe

  • For OracleDB exporter:

    destination-folder\oracledb_exporter_windows\jp1ima\bin\oracledb_exporter.exe

<arguments>

Specify the program arguments (the arguments to be passed to the executable file to be launched).

If you want to change the value, restart the service after changing the value.

Y

Change the settings when you want to change the arguments.

  • For Prometheus server

    For prometheus.exe parameters, see prometheus Command Options.

    --Config.file = "Agent-path/conf/jpc_prometheus_server.yml"

  • For Alertmanager

    About arguments of alertmanager.exe, see alertmanager command options.

  • For Windows exporter

    About arguments of windows_exporter.exe, see windows_exporter command options.

  • For Blackbox exporter

    About arguments of blackbox_exporter.exe, see blackbox_exporter command options.

  • For JP1/IM agent management base (imbase and imbaseproxy) and JP1/IM agent control base (imagent, imagentproxy, and imagentaction)

    ■For normal hosts

    None

    ■For cluster environments

    -hostname logical host name

  • For Fluentd

    For details about the parameters of fluentd command, see fluentd command options

  • For Yet another cloudwatch exporter:

    For details on the ya_cloudwatch_exporter.exe arguments, see ya_cloudwatch_exporter command options.

  • For Promitor Scraper:

    For details on the promitor_scraper.exe arguments, see promitor_scraper command options.

  • For Promitor Resource Discovery:

    For details on the promitor_resource_discovery.exe arguments, see promitor_resource_discovery command options.

  • For Script exporter:

    For details on the script_exporter.exe arguments, see script_exporter command options.

  • For OracleDB exporter

    For information about oracledb_exporter.exe arguments, see oracledb_exporter command options.

<startmode>

Specify the startup type (Windows service start mode) (optional).

Specify one of the following values:

  • Automatic

  • Manual

If you want to change the value, uninstall the service once, change the value, and then reinstall the service.

Y

  • For Prometheus server,Alertmanager,Windows exporter,Blackbox exporter, JP1/IM agent control base (imagent, and imagentproxy), Fluentd, and OracleDB exporter

    For clustered operation, specify Manual.

  • For Prometheus server,Alertmanager,Windows exporter, Blackbox exporter, Yet another cloudwatch exporter, Promitor Scraper, Promitor Resource Discovery, Script exporter, JP1/IM agent control base (imagent, and imagentproxy) and Fluentd

    Automatic

  • For JP1/IM agent management base (imbase and imbaseproxy)

    Manual

<logpath>

Specify the log output destination directory (the directory where the log file will be created).

If specified, the directory where the configuration file exists is the default.

If you want to change the value, restart the service after changing the value.

Y

--

Set up automatically during setup.

<log mode="roll-by-size">

The log output mode is roll-by-size mode. It operates in the same way as append mode, but if the value set for log file size is exceeded, it will be rolled to myapp.1.out.log, myapp.2.out.log, etc.

N

--

--

<sizeThreshold>

Specify it in KB when changing the log file size (rotation threshold).

If you want to change the value, restart the service after changing the value.

N

Change Setup when you are prompted to change Value from the support desk.

10240

<keepFiles>

Specify this when changing the number of log planes (the number of role files to keep).

A log with the specified number of sides + 1 side is created.

If you want to change the value, restart the service after changing the value.

Value that can be Setup is 7 to 511.

Y

Change Setup when you are prompted to change Value from the support desk.

7 (99 for Fluentd only)

<stoptimeout>

Specifies the wait time to stop the service (the maximum amount of time to wait after issuing a stop request to the program before the service is stopped).

If you want to change the value, restart the service after changing the value.

Y

Change the settings when you want to change the waiting time for an outage.

  • For Prometheus server

    110sec

  • For Alertmanager,Windows exporter,Blackbox exporter, Yet another cloudwatch exporter, Promitor Scraper, Promitor Resource Discovery, Script exporter, and Fluentd

    60sec

  • For JP1/IM agent management base (imbase), and JP1/IM agent control base (imagent)

    90sec

  • For JP1/IM agent management base (imbaseproxy), and JP1/IM agent control base (imagentproxy)

    140sec

  • For OracleDB exporter

    60sec

Legend:

Y: Changeable, N: Not changeable, --: Not applicable

Legend:

Y: Changeable, N: Not changeable, --: Not applicable

Legend:

Y: Changeable, N: Not changeable, --: Not applicable

Legend:

Y: Changeable, N: Not changeable, --: Not applicable

Legend:

Y: Changeable, N: Not changeable, --: Not applicable

Legend:

Y: Modifiable, N: Not modifiable, --: Not applicable

Legend:

Y: Changeable, N: Not changeable, --: Not applicable

Legend:

Y: Changeable, N: Not changeable, --: Not applicable