13.2.4 Procedure required to add, change, and delete targets for monitoring
The following shows the procedure required to add, change, and delete targets for monitoring for add-on programs provided by IM Exporter.
For details on how to edit configuration files, see 1.21.2(1)(a) Edit the configuration files (for Windows) and 2.19.2(1)(a) Edit the configuration files (for Linux) in the manual JP1/Integrated Management 3 - Manager Configuration Guide.
- Organization of this subsection
(1) Exporter
Add, change, and delete Exporter monitoring targets using the following procedures.
|
Exporter |
Procedure |
|---|---|
|
Windows exporter |
To add, change, or delete monitoring targets (processes), edit the Windows exporter configuration file (jpc_windows_exporter.yml)#. |
|
Process exporter |
To add, change, or delete Process exporter monitoring targets (processes), edit the Process exporter configuration file (jpc_process_exporter.yml)#. |
|
Yet another cloudwatch exporter |
Set the jp1_pc_nodelabel tag for the AWS resource you want to set as a monitoring target. For details, see the description under 2.19.2(7)(e) Setting an AWS resource as a monitoring target (optional) in the manual JP1/Integrated Management 3 - Manager Configuration Guide. |
|
Promitor |
To add, change, or delete Promitor monitoring targets (Azure resources), edit the Promitor configuration file (metrics-declaration.yaml)# and the Promitor Resource Discovery configuration file (resource-discovery-declaration.yaml)#. |
|
Container monitoring through user-specific Prometheus |
To add, change, or delete monitoring targets (Kubernetes resources), edit the Prometheus configuration file on the user operating environment. For details, see the description under (e) Configuring scraping targets (optional) of 10.1.2(7) Setting up container monitoring in the manual JP1/Integrated Management 3 - Manager Configuration Guide. |
|
Script exporter |
To add, change, or delete a user-specified script, edit the Script exporter configuration file (jpc_script_exporter.yml)#. To add, change, or delete monitoring targets (scripts) when the scrape specification is defined in the file_sd_config method, edit the Prometheus configuration file (jpc_prometheus_server.yml)#. These changes are not required if the scrape specification is defined in the http_sd_config method. |
- #
-
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.
(2) Log metrics feature
The following shows how to add, change, and delete monitoring targets for the log metrics feature.
(a) Adding monitoring targets for the log metrics feature
- - Adding a log metric to be monitored in Fluentd
-
To add log metrics to be monitored in Fluentd, add a new <metric> definition in parallel to the existing <metric> definition in the filter plug-in feature definition, or the output plug-in feature definition in the log metrics definition file.
- - Adding log metrics shown in trend information in the JP1/IM - Manager integrated operation viewer
-
To add log metrics scraped from Fluentd as log metrics shown in trend information in the JP1/IM - Manager integrated operation viewer, add the definition for the relevant metric in the user-specific metric definition file.
(b) Changing monitoring targets for the log metrics feature
- - Changing a log metric to be monitored in Fluentd
-
To change log metrics to be monitored in Fluentd, change the contents of the <metric> definition in the filter plug-in feature definition, or the output plug-in feature definition in the log metrics definition file.
- - Changing log metrics shown in trend information in the JP1/IM - Manager integrated operation viewer
-
To change log metrics that are scraped from Fluentd and shown in trend information in the JP1/IM - Manager integrated operation viewer, change the definition for the relevant metric in the user-specific metric definition file.
(c) Deleting monitoring targets for the log metrics feature
- - Deleting a log metric being monitored in Fluentd
-
To delete a log metric being monitored in Fluentd, delete or comment out all related definitions in the log metrics definition file.
- - Deleting log metrics shown in trend information in the JP1/IM - Manager integrated operation viewer
-
To delete log metrics scraped from Fluentd from being shown in trend information in the JP1/IM - Manager integrated operation viewer, delete or comment out the definition for the relevant metric in the user-specific metric definition file.