UD Agent - install / Uninstall logs shold contain data like hostname, fqdn, IP address.

Idea ID 1645006

UD Agent - install / Uninstall logs shold contain data like hostname, fqdn, IP address.

 UD Agent - install / Uninstall logs - there should be information about hostname, fqdn, IP address .... etc. for the node where the agent is installed / uninstalled. That would help  in case of troubleshooting big environments when more agents failed for some reason.

8 Comments
Honored Contributor.
Honored Contributor.

Do you refr to the communication log? The trigger for these job is the node, so you know what node the job failed on… And from the node CI you can get the host name or anything else. IP address is already passed to the job as one of the parameters and should appear in the log already. And if other things also need to be in the log, the hostname. FQDN, etc. from the node can be brought as extra job parameters – this way just like the IP address, they will appear in the communication log. So this could at least be used as a workaround for now.

Let me know if it makes sense, or please add some more data.

Regular Contributor.
Regular Contributor.

Hi,

Iforgot to mention that customer installing UDA manualy, which mean that no communicatins logs are created.

BR.

 

 

Honored Contributor.
Honored Contributor.

Please describe the exact scenario of the installation , usually there would be ways to extract this data from the tools you leverae.

Honored Contributor.
Honored Contributor.
Status changed to: Waiting for Votes

Please provide more info as requested below.

Honored Contributor.. Honored Contributor..
Honored Contributor..

Hello,

the scenario is pretty simple. Large organisations often install UDAs by means of other tools (like Microsoft SCCM etc.) not via UCMDB/UD. And when you install thousands of UDAs then same of the installations fail. That happens. However you need to know why it happens and where. The common method is collect installation logs and analyzee them. In bulk. Unfortunately current installation log if full of useless data (like references to Peregrine Systems etc.) but misses very important data that identifies the system where the installation failed. The installation log should contain the following elements :

operation type : installation, reinstallation, uninstallation, uninstallation full
hostname : hostname of system where the UDA is being installed
IP : current IP of the system where the UDA is being installed
FDQN : fully qualified domain name of the system where the UDA is being installed
user : idetification of user account under which the installation was performed

This data are essential for further investigation and debugging of the cases, when UDA deployment failed. 
That is the story - make the mass deployment of UDAs better.

Ivan

 

 

Outstanding Contributor.
Outstanding Contributor.

Can we take this a step further and get some actual UI that we can use to manage the agents across an enterprise? Perhaps something simple such as the picture below which I modified from the agent dashboard of another product that we use here:

agent_dashboard.png 

Theoretically, clicking on details should show the hosts in each category and within each host you should have accessible agent logs as described by Ivan.

 

Honored Contributor.. Honored Contributor..
Honored Contributor..

Hmm looks nice. Indeed. This topic shoudl deserve attention from both sides : )

a) from agent deployment and status collection (not deployment via UCMDB but via SCCM, Tivoli etc. - thus "manual" installation but in bulk 🙂

b) from GUI presenting the information about agents in clear and drill-down enabled format (like in the picture above) 

Ivan

Micro Focus Expert
Micro Focus Expert
Status changed to: Archived

This idea is being archived due to inactivity. Archived ideas may be commented upon but may not receive kudos. Archived ideas may be re-opened based on community input.

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.