https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/integration_template/im_template/index.html Recent content in 4.9.2 JP1/IM on JP1 Cloud Service/Operations Integration User's Guide Hugo -- gohugo.io en https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/integration_template/im_template/im_monitor/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/integration_template/im_template/im_monitor/index.html The linkage templates allow Ops I to be linked with the JP1/IM system management functions, and to obtain and update the JP1/IM setting file called “common exclusion conditions extension definition file (common_exclude_filter.conf)”. This allows JP1/IM jobs to be executed from Ops I workflows for control over the start and cancellation of monitoring deterrence according to specific conditions. For example, this can be used to prevent alerts from being generated when stopping the server for maintenance. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/integration_template/im_template/im_incident/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/integration_template/im_template/im_incident/index.html This function allows events managed in JP1/IM to be registered as Ops I tickets. This allows status management and ticket handling to be performed in Ops I. (1) Prerequisites The JP1/IM addresses must be added as permitted inbound IP addresses in Ops I. Users who configure the settings must meet the following conditions. The Ops I Primitive role “user_admin” is assigned (for issuing Ops I tokens). The Ops I Primitive role “itsm_viewer” is not assigned (for creating tickets).