Hitachi

JP1 Version 13 JP1/Integrated Management 3 - Manager Command, Definition File and API Reference


11.1.1 Cloud service log linkage tool list

Table 11‒1: List of cloud service log linkage tools

Cloud services to be linked

Tool name

File name

Types of logging that can be registered as JP1 events

Amazon Web Services (AWS)

AWS Lambda linkage tool

(JP1 event. register command-compatible#1)#3

jp1_sendevent_cmd_aws.zip#4

(Files under the Lambda folder)

  • EC2 instance logging

  • Trail logging recorded by CloudTail

AWS CloudWatch linkage tools

(JP1Event Registration Command Supported Version#1)#3

jp1_sendevent_cmd_aws.zip#4

(Files under the CloudWatch folder)

  • Alarms raised from AWS CloudWatch

AWS Lambda linkage tool

(JP1/IM REST compatible version #2) #3

jp1_sendevent_im3_aws.zip #4

  • EC2 Instance Logs

  • Trail logs recorded by CloudTrail

Azure

Azure linkage tool

(JP1 event. register command-compatible #1) #3

jp1_sendevent_cmd_azure.zip #4

  • Logging #5 collected by Azure VM

  • Azure Activity Log #5

  • Logging #5 collected by Azure WebApps,Azure Functions

  • Azure Monitor metric #6

Azure linkage tool

(JP1/IM REST compatible version #2) #3

jp1_sendevent_im3_azure.zip #4

#1

In the JP1 event registration command compatible version, when you run the jevsend command on an environment connected by VPN with the cloud service of the link source, you can register the log of the original cloud service as JP1/Base as a JP1 event and link it.

#2

In JP1/IM REST compatibility, you can use JP1/IM-Manager (Intelligent Integrated Management Base) event publishing REST API to JP1 the logging of the cloud service you are collaborating with to register as an event.

#3

The linked JP1 events can be referenced from JP1/IM-View.

In addition, it can be mapped to the same IM management node as the performance monitoring at the JP1/IM - Agent, displayed from the Integrated Operations Viewer, and referenced in combination with other performance information. To map to an IM management node, an extended attribute must be granted to the JP1 event to be issued. For the extended attributes to be granted, see "3.14.7 Collaboration with Cloud Services" in the manual "JP1/Integrated Management 3 - Manager Overview and System Design Guide".

#4

A compressed file that contains a text file (version.txt) containing version of the tooling.

#5

Data that can be set as log alerts stored in the Log Analytics workspace or Application Insights (Microsoft.Insights/LogAlert).

#6

Data that can be Setup as metric alerts (AzureMonitorMetricAlert).