10.1.3 Configuring the feature for making processes run as services

When you install a new integrated agent, processes for IM Exporter-provided add-on programs are configured to be run as services while the installation script is being executed. Automated startup and termination settings are enabled, and services are in the stopped state right after its installation.

The following shows which services are registered in each OS when IM Exporter add-on programs are configured to be run as services.

Note that the log metrics feature itself cannot be run as a service as it is a Fluentd plug-in. For details on which Fluentd services are registered, see the section describing 10. starting and stopping JP1/IM - Agent in the manual JP1/Integrated Management 3 - Manager Administration Guide.

Organization of this subsection

(1) Which services are registered
(2) Setup procedure
(3) Starting and stopping services

(1) Which services are registered

- In Windows

When the installation script for the add-on programs is run, the IM Exporter add-on programs are registered as Windows services according to the definitions in the service definition file.

This process uses the same service definition file and user account used for logging on the services as JP1/IM - Agent.

Table 10‒8: Services registered in the Windows environment
Label	Service name	Service role	Name of the running process	Number of processes
JP1/IM3-Agent Windows metric collector	jpc_windows_exporter	Windows exporter	windows_exporter.exe	1
JP1/IM3-Agent Windows metric collector	jpc_windows_exporter	Windows exporter	windows_exporter_service.exe	1
JP1/IM3-Agent AWS metric collector	jpc_ya_cloudwatch_exporter	Yet another cloudwatch exporter	ya_cloudwatch_exporter.exe	1
JP1/IM3-Agent AWS metric collector	jpc_ya_cloudwatch_exporter	Yet another cloudwatch exporter	ya_cloudwatch_exporter_service.exe	1
JP1/IM3-Agent Azure metric collector	jpc_promitor_scraper	Promitor scraper	promitor_scraper.exe	1
JP1/IM3-Agent Azure metric collector	jpc_promitor_scraper	Promitor scraper	promitor_scraper_service.exe	1
JP1/IM3-Agent Azure resource discovery	jpc_promitor_resource_discovery	Promitor Resource Discovery	promitor_resource_discovery.exe	1
JP1/IM3-Agent Azure resource discovery	jpc_promitor_resource_discovery	Promitor Resource Discovery	promitor_resource_discovery_service.exe	1
JP1/IM3-Agent Script metric collector	jpc_script_exporter	Script exporter	script_exporter.exe	1
JP1/IM3-Agent Script metric collector	jpc_script_exporter	Script exporter	script_exporter_service.exe	1

- In Linux

When the installation script for add-on programs is run, the IM Exporter add-on programs are registered with Linux systemd according to the definitions in the unit definition file.

This process uses the same unit definition file as JP1/IM - Agent.

Table 10‒9: Services registered in the Linux environment
Unit name	Service role	Name of the running process	Number of processes
jpc_process_exporter	Process exporter	process_exporter	1
		rotatelogs	1
		sh	3
jpc_ya_cloudwatch_exporter	Yet another cloudwatch exporter	ya_cloudwatch_exporter	1
		rotatelogs	1
		sh	3
jpc_promitor_scraper	Promitor Scraper	promitor_scraper	1
		rotatelogs	1
		sh	3
jpc_promitor_resource_discovery	Promitor Resource Discovery	promitor_resource_discovery	1
		rotatelogs	1
		sh	3
jpc_script_exporter	Script exporter	script_exporter	1
		rotatelogs	1
		sh	3

To Page Top

(2) Setup procedure

For details on enabling or disabling service registration and automated startup, see the section describing setup of JP1/IM - Agent.

To Page Top

(3) Starting and stopping services

For details on how to start and stop services, see the section describing 10. starting and stopping JP1/IM - Agent in the manual JP1/Integrated Management 3 - Manager Administration Guide.

Note that the log metrics feature itself cannot be started or stopped because it is a Fluentd plug-in. The log metrics feature starts or stops as Fluentd starts or stops.

To Page Top