Hitachi

JP1 Version 13 JP1/Integrated Management 3 - Manager Overview and System Design Guide


3.14.7 Linkage for Monitoring Cloud Services Logs

Organization of this subsection

(1) Introduction

JP1/IM includes the Cloud Service Log Linkage Tool, which registers the following cloud service logs as JP1 events to JP1/IM-Manager when managing the operation of server instance's OS, middleware, applications, and other devices in the cloud. For details about how to monitor the performance of the cloud, see 9.5 Monitoring function by JP1/IM - Agent.

■When linking with AWS

Logs saved by the service that monitors logs from resources on Amazon CloudWatch Logs (AWS are registered as JP1 events. Tools that can be linked with JP1/IM-Manager, JP1/Base are provided.

■When linking with Microsoft Azure

Alerts generated in Azure Monitor (System monitoring services that are provided on Azure) are registered as JP1 events to provide tools that can be linked to JP1/IM-Manager, JP1/Base.

The tools for linking to cloud services include the following features:

■Prerequisites
  • Intelligent Integrated Management Base must be enabled if you are using a JP1/IM REST compatible tool or if you are using file download capabilities to download the tool from a link.

  • The prerequisites for the tools must meet the prerequisites described in 11. Cloud Services Log Linkage Tool in JP1/Integrated Management 3-Manager Command, Definition File and API Reference manual.

  • IM management node to be mapped exists beforehand when JP1 event that is linked to JP1/IM with JP1/IM REST compatible version of the tool is mapped to the same IM management node as the operation performance monitoring in JP1/IM-Agent and displayed in integrated operation viewer. For AWS linkage, IM management node of Azure monitoring exporter must exist for Yet another cloudwatch exporter,Azure linkage.

For more information about the Cloud Services Log Linkage Tool, see 11. Cloud Services Log Linkage Tool in JP1/Integrated Management 3-Manager Command, Definition File and API Reference manual.

(2) Construction procedure

(a) Deploying tools to collaboration sources

Tools imported by JP1/IM-Manager can be obtained by copying the files directly to the cloud service side of the collaboration source or by downloading the files from the manager host. For downloading, see 3.13 Distribution get capabilities (file download capabilities). Here is an URL of a deployment:

http://JP1/IM - Manager-hostname:Intelligent-Integrated-Management-Base-port-number/download/jp1_cloudwatch_tool/tool-filename #

#

For details about the tool filename, see 11. Cloud Services Log Linkage Tool in JP1/Integrated Management 3-Manager Command, Definition File and API Reference.

(b) Settings at the collaboration source

If you unzip the extracted files to the source, the sendevent_im2 (JP1 Event Linkage Tool Directory) will be expanded. Use Python scripts and definition files under the expanded folder to configure the settings according to the required settings and steps described in 11. Cloud Services Log Linkage Tool in JP1/Integrated Management 3-Manager Command, Definition File and API Reference.

  • When filtering logs to be linked as JP1 events by regular expressions

    Set in the event exclusion file for each tool. For more information, see section 11, Cloud Services Log Linkage Tool in JP1/Integrated Management 3-Manager Command, Definition File and API Reference.

    If you do not specify this setting (by default), all logs will be linked instead of filtering.

  • Assigning any extended properties to JP1 events that are linked

    Set in the event definition file of each tool. For more information, see section 11, Cloud Services Log Linkage Tool in JP1/Integrated Management 3-Manager Command, Definition File and API Reference.

    The following extended attributes are added to JP1/IM REST version of JP1/IM linked JP1 events when they are mapped to the same JP1/IM-Agent performance monitoring IM management node and displayed in integrated operation viewer.

    Attribute type

    Item

    Attribute name

    Description

    Common information

    Severity

    SEVERITY

    Depending on the contents of the JP1 event, specify one of the following values:

    • "Emergency"

    • "Alert"

    • "Critical"

    • "Error"

    • "Warning"

    • "Notice"

    • "Information"

    • "Debug"

    Product name

    PRODUCT_NAME

    "/HITACHI/JP1/JPCCS2" or "/HITACHI/JP1/JPCCS2/xxxx"

    xxxx is user-defined. Match the mapping destination. #3

    Object type

    OBJECT_TYPE

    "ALARM"

    Object name

    OBJECT_NAME

    Alert name

    Match the mapping destination. #3

    Event type

    OCCURRENCE

    "NOTICE"

    Originating host name

    JP1_SOURCEHOST

    Match the mapping destination. #3

    Unique information

    PP

    PPNAME

    "/HITACHI/JP1/JPCCS2"

    Hostname of integrated agent

    JPC_PROMETHEUS

    Match the mapping destination. #3

    Scrape job

    JPC_JOB

    Match the mapping destination. #3

    jp1_pc_nodelabel

    JPC_NODELABEL

    Match the mapping destination. #3

    Exporter name

    JPC_EXPORTER

    Match the mapping destination. #3

    jp1_pc_remote_monitor_instance

    JPC_REMOTE_

    MONITOR_INSTANCE

    Match the mapping destination. #3

    AWS service-name #1

    JPC_AWS_SERVICE

    AWS service name

    Set only when using the Cloud service log linkage tool (JP1 and AWS linkage).

    Match the mapping destination. #3

    AWS accounting #1

    JPC_AWS_ACCOUNT

    AWS account-string

    Set only when using the Cloud service log linkage tool (JP1 and AWS linkage).

    Match the mapping destination. #3

    AWS region name #1

    JPC_AWS_REGION

    Region-name of AWS monitored by Yet another cloudwatch exporter

    Set only when using the Cloud service log linkage tool (JP1 and AWS linkage).

    Match the mapping destination. #3

    Azure service-name #2

    JPC_AZURE_SERVICE

    Azure service name

    Set only when using the Cloud service log linkage tool (JP1 and AWS linkage).

    Match the mapping destination.

    For more information, see 12.5.1(5)(a) Attributes of JP1 events issued during performance data monitoring.

    Azure tenancy #2

    JPC_AZURE_TENANT

    Azure tenant string

    Set only when using the Cloud service log linkage tool (JP1 and AWS linkage).

    Match the mapping destination.

    For more information, see 12.5.1(5)(a) Attributes of JP1 events issued during performance data monitoring.

    Azure subscription-name #2

    JPC_AZURE_SUBSCRIPTION

    Azure subscription string

    Set only when using the Cloud service log linkage tool (JP1 and AWS linkage).

    Match the mapping destination.

    For more information, see 12.5.1(5)(a) Attributes of JP1 events issued during performance data monitoring.

    Azure Resource Group Name #2

    JPC_AZURE_RESOURCEGROUP

    Azure resource group-name

    Set only when using the Cloud service log linkage tool (JP1 and AWS linkage).

    Match the mapping destination.

    For more information, see 12.5.1(5)(a) Attributes of JP1 events issued during performance data monitoring.

#1

Specifies that Yet another cloudwatch exporter is to be displayed in IM management node.

#2

Specifies that Azure monitor exporter is to be displayed in IM management node.

#3

See 3.2.3(1) Attributes of JP1 events that monitor and issue performance data in JP1/Integrated Management 3-Manager Command, Definition File and API Reference Manual.

(3) Troubleshooting

There is no additional logfile on JP1/IM-Manager. The log of the cloud service log linkage tool is output to the cloud service side where the tool was set up. For more information, see section 11, Cloud Services Log Linkage Tool in JP1/Integrated Management 3-Manager Command, Definition File and API Reference.