12.2.2 JP1/IM - Agent log information

(1) Prometheus server log

Prometheus server log is output.

Upper limit of log size and number of planes

• For Windows

  Specify in service definition file.

• For Linux

  Specify in unit definition file.

For details on the specification procedure, see service definition file and unit definition file in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Output destination

• For Windows

  Agent-path^#\logs\prometheus_server\jpc_prometheus_server_service.(err|out).log

  #: For a cluster, replace it with "shared-folder\jp1ima".

• For Linux

  /opt^#/jp1ima/logs/prometheus_server/prometheus_service

  #: For a cluster, replace it with "shared-directory".

Output format

Prometheus server outputs text data that is output to stdout or stderr during operation.

To Page Top

(2) Alertmanager log

Alertmanager log is output.

Upper limit of log size and number of planes

• For Windows

  Specify in service definition file.

• For Linux

  Specify in unit definition file.

For details on the specification procedure, see service definition file and unit definition file in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Output destination

• For Windows

  Agent-path^#\logs\alertmanager\jpc_alertmanager_service.(err|out).log

  #: For a cluster, replace it with "shared-folder\jp1ima".

• For Linux

  /opt^#/jp1ima/logs/alertmanager/alertmanager_service

  #: For a cluster, replace it with "shared-directory".

Output format

Alertanager outputs text data output to standard output or standard error output while running.

To Page Top

(3) Exporter Logs

Exporter logs will be output.

Upper limit of log size and number of planes

• For Windows

  Specify in service definition file.

• For Linux

  Specify in unit definition file.

For details on the specification procedure, see service definition file and unit definition file in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Output destination

• For Windows

  Agent-path^#\logs\Exporter-name\jpc_Exporter-name_service.(err|out).log

  #: For a cluster, replace it with "shared-folder\jp1ima".

• For Linux

  /opt^#/jp1ima/logs/Exporter-name/Exporter-name_service

  #: For a cluster, replace it with "shared-directory".

Output format

Exporter outputs text data output to standard output or standard error output while running.

To Page Top

(4) Service Control Log

• For Windows

  Log is output when the service is started or stopped.

• For Linux

  No log is output.

Upper limit of log size and number of planes

Rotate when the log reaches a certain size. You cannot specify the maximum log size and the number of planes.

Output destination

• For Windows

  Agent-path^#\logs\prometheus\jpc_prometheus_server_service.wrapper.log

  Agent-path^#\logs\alertmanager\jpc_alertmanager_service.wrapper.log

  Agent-path^#\logs\Exporter-name\jpc_Exporter-name_service.wrapper.log

  Agent-path^#\logs\fluentd\jpc_fluentd_service.wrapper.log

  Agent-path^#\logs\imagent\jpc_imagent_service.wrapper.log

  Agent-path^#\logs\imagentproxy\jpc_imagentproxy_service.wrapper.log

  Agent-path^#\logs\imagentaction\jpc_imagentaction_service.wrapper.log

  #: For a cluster, replace it with "shared-folder\jp1ima".

Output format

The text data output by Windows service program is output.

Timing and size of output

The following table summarizes the timing and size of the output to the service control log.

Opportunity	A measure of size (bytes)	Output example
Starting the Service	750	2021-11-22 14:18:48,135 DEBUG - Starting WinSW in service mode 2021-11-22 14:18:48,394 INFO - Starting prometheus.exe --config.file="jpc_prometheus_server.yml" --web.read-timeout=5m --web.max-connections=10 --web.enable-lifecycle --storage.tsdb.path="data/" --storage.tsdb.retention.time=0d --storage.remote.flush-deadline=2m --rules.alert.for-outage-tolerance=1h --rules.alert.for-grace-period=10m --rules.alert.resend-delay=1m --alertmanager.notification-queue-capacity=10000 --log.level=info --log.format=logfmt 2021-11-22 14:18:50,805 INFO - Started process 17384 2021-11-22 14:18:50,826 DEBUG - Forwarding logs of the process System.Diagnostics.Process (prometheus) to WinSW.SizeBasedRollingLogAppender
Stopping the Service	300	2021-11-22 14:12:04,083 INFO - Stopping jpc_prometheus 2021-11-22 14:12:04,084 DEBUG - ProcessKill 16492 2021-11-22 14:12:04,108 DEBUG - Stopping process 16492... 2021-11-22 14:12:04,141 DEBUG - Process 16492 canceled with code 0. 2021-11-22 14:12:04,176 INFO - Finished jpc_prometheus

How to delete

Move or rename the log file and save it. After saving, the program creates a log file when the user performs an operation to output the log. There is no need to stop the service when saving log files.

The saved file is deleted manually when it is judged to be unnecessary.

To Page Top

(5) Fluentd log

Fluentd log is output.

Upper limit of log size and number of planes

• For Windows

  Specify in service definition file.

• For Linux

  Specify in unit definition file.

For details on the specification procedure, see service definition file and unit definition file in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Output destination

• For Windows

  Agent-path^#\logs\fluentd\jpc_fluentd_service.(err|out).log

  #: For a cluster, replace it with "shared-folder\jp1ima."

• For Linux

  /opt^#/jp1ima/logs/fluentd/fluentd_server

  #: For a cluster, replace it with "shared-directory".

Output format

Fluentd outputs text data that is output to stdout or stderr during operation.

To Page Top

(6) Command log

The command log is output.

Upper limit of log size and number of planes

The maximum log size and the number of planes are determined for each comman, cannot be changed.

Output destination

• For Windows

  Agent-path^#\logs\tools\command-name.*

#

For clusters, there are commands that output to physical disks and commands that output to shared disks. If the command is to be exported to a shared disk, replace it with "shared-folder\jp1ima".

• For Linux

  /opt^#/jp1ima/logs/tools\command-name.*

#

For clusters, there are commands that output to physical disks and commands that output to shared disks. If the command is output to a shared disk, replace it with "shared-directory".

Output format

Date log-contents

To Page Top

(7) JP1/IM - Agent control base log

To Page Top