13.2.2 Procedure required to change the Exporter listening port
- Organization of this subsection
(1) Changing the listening port for integrated agent processes
This procedure requires work on the integrated agent host running the process for changing the listening port number, and the integrated manager host.
Do not specify a port used by other processes as the listening port number. For details of ports used by JP1/IM - Agent, check the command line options or configuration files for each process listed in the unit definition file or service definition file described in the table below. For details on ports used by other products, see the documentation provided with the product.
To change the Exporter port used by add-on programs provided with IM Exporter, change the port used by JP1/IM - Agent described in the table below.
For details on how to change the port using command line options, see the description on 1.21.2(1)(c) Change command-line options (for Windows) and 2.19.2(1)(c) Change command-line options (for Linux) in the manual JP1/Integrated Management 3 - Manager Configuration Guide. For details on how to change the configuration file, see the description on 1.21.2(1)(a) Edit the configuration files (for Windows) and 2.19.2(1)(a) Edit the configuration files (for Linux) and 2.19.2(1)(a) Edit the configuration files (for Linux) in the manual JP1/Integrated Management 3 - Manager Configuration Guide.
|
Process |
Section describing the port used by JP1/IM - Agent |
Notes |
|---|---|---|
|
Process exporter |
--web.listen-address=host-name:port-number |
|
|
Windows exporter |
--telemetry.addr=host-name:port-number |
For details, see the description under (a) Changing ports (optional) of 1.21.2(5) Windows exporter setup in the manual JP1/Integrated Management 3 - Manager Configuration Guide. |
|
Yet another cloudwatch exporter |
-listen-address=host-name:port-number |
For details, see the description under (a) Changing ports (optional) of 2.19.2(7) Yet another cloudwatch exporter setup in the manual JP1/Integrated Management 3 - Manager Configuration Guide. |
|
Promitor Scraper |
Promitor Scraper runtime configuration file (runtime.yaml) |
This is changed in the Promitor Scraper runtime configuration file (runtime.yml)#, not in command line options. Changes to this configuration file also require changes to the Promitor discovery configuration file (jpc_file_sd_config_promitor.yml). |
|
Promitor Resource Discovery |
Promitor Resource Discovery runtime configuration file (runtime.yaml) |
This is changed in the Promitor Resource Discovery runtime configuration file (runtime.yml)#, not in command line options. Changes to this configuration file also require changes to the Promitor Scraper runtime configuration file (runtime.yml). |
|
Script exporter |
--web.listen-address=host-name:port-number |
|
- #
-
For details, see the section describing the relevant definition file under 10. IM Exporter definition files in the manual JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.