On behalf of CA Technologies, we appreciate your business and the opportunity to provide you with innovative software and services. As part of our ongoing commitment to customer success, we regularly release updated versions of our products which include Service Operations Insight integration updates. To ensure our user community is continually aware of any new and updated connectors, we'll be announcing them here in this forum.
Today, we are pleased to announce that a new version of CA Unified Infrastructure Management (CA UIM) Connector for CA Service Operations Insight (CA SOI) have been updated and is now available from the CA Service Operations Insight Connectors page.
Details of the new CA Unified Infrastructure Management (UIM) Connector 3.6.0 :
During the connector installation, you are prompted to provide the CA UIM UMP configuration details. So, you can launch CA UIM UMP webpage from CA SOI to view the alarms or a service or CI details. This feature is supported only in CA SOI 3.3 CU2 and 4.0 CU1. For more information, see Launch CA UIM UMP from CA SOI.
During the installation, you can provide the queue name configured in CA UIM. If you have not configured a queue name in CA UIM, you can provide a name during the installation and later configure the same name in CA UIM.
Some of the Logmon probe alerts are not mapped to CIs in CA UIM Connector because of hostname mismatch between CI and alarm or CA UIM data mismatch. Therefore, in SOI Console hostname of the alert was mentioned as Unknown.
The Release Note and documentation are available from the Wiki based product documentation.
If you require assistance, please contact CA Customer Care online at http://www.ca.com/us/customer-care.aspx where you can submit an online request using the Customer Care web form: https://communities.ca.com/web/guest/customercare. You can also call CA Customer Care at +1-800-225-5224 in North America or see http://www.ca.com/phone for the local number in your country.
The logmon is now showing the name of the machine where the probe is running from and not the 'override' value.
This is better than the 'unknown' but it is disabling the ability to use the override value for alarms.