Add version number of UD Agent in communication logs

Idea ID 1790021

Add version number of UD Agent in communication logs

In the communication log for any discovery if the UD Agent is being used as the protocol, we should print out the version of the UD Agent in the communication log.

6 Comments
Micro Focus Expert
Micro Focus Expert

We can use the output from the UDA parameter --version that was implemented in CP27 https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/LID/QCCR1H121222

This would be useful as sometimes we can have a failing discovery because the UDA version is not aligned with the UCMDB and UD versions and the easy fix would be to upgrade that UD agent.

Example: if Host Connection by shell over UDA fails than we can check in the CommLog what's the UDA version printed right after the connection successful event. If the version is too old then work on the UDA upgrade/update first.

Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team

Micro Focus Expert
Micro Focus Expert

We may have 2 options:

1. use the --version paramter to print somewhere in the CommLog the UDA version. 

Pro: we are using an existing functionality. The output will be printed in the CommLog. Easy to implement.

Con: The version information will be printed after the OS identification flow as the parameter has a different format depending on the OS flavor ( \version for NT, --version for Unix)

2. After the connection is successful over the UDA protocol, send back to the Probe Gateway the UDA version information.

Pro: the UDA version is printed in the CommLog immediately after a successful connection independent on the OS flavor. We don't need permissions to run the OS identification or the discagnt --version commands.

Con: this functionality doesn't exist and needs to be written from scratch.

Outstanding Contributor.
Outstanding Contributor.

Another option is to add the Agent version to the options map in the aioptionrc file or registry on Windows. The communication log already displays this information when it executes the getOptionsMap command.

Micro Focus Expert
Micro Focus Expert
Status changed to: Accepted

Great news, this idea has been accepted on our product roadmap. Subscribe to receive updates. (This is not a formal commitment, and subject to change)

Micro Focus Expert
Micro Focus Expert
Status changed to: Delivered

This idea has been implemented in product release CMS 2020.02. Check out the release notes for details. Thanks to all of our contributors for helping us continue to improve our products!

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.