Highlighted
Absent Member.. Absent Member..
Absent Member..
371 views

UCMDB Support Tip: Flow of logs (probe -> server)

This information is written in the logs in the following order (based on UCMDB 9.x):

 

1) Communication log. The communication log contains the Object Stateholder Vector (OSH) created by the jython script. You will see this vector only if you enable results for communication log. Results for communication logs can be enabled for the communication logs by right click on the job -> Go to adapter -> click on the 'Adapter Configuration' tab in the top right hand corner -> set the 'Include results in communication log’ to ‘Yes’ and ‘Create communication log’ to ‘Always’. The results vector will show the temp id of the CIs.

 

2) probeMgr-result-processing.log. The communication log contains the OSH in old format. At the result processing layer, the OSH is converted into the new format if required. For example, if the OSH contains CI of Type ‘host’, it will be converted into ‘node’. The purpose of this is to convert topology created based on old class model into new one. [This applies to UCMB 9.x only. Things might work differently on 10.x.]

 

3) WrapperProbeGw.log. This is where the results are sent to the server.

 

4) Mam.autodiscovery.log. If you put this log in debug mode, you can see the vector that the server receives. This log can be helpful in troubleshooting issues. For example if a CI from an external source is not reaching the DB, the first thing you can do is to find out if the CI even reached the server or not. Putting this log in debug will clarify that.

 

5) Reconciliation logs. This is where the reconciliation happens.

 

6) Cmdb.model.audit.short.log. This log file will contain data that was sent to the model update (all the CIs in the system or the model will be updated with certain data). This log will also show details such as the amount of CIs that were sent and their CI Types for example 3 Unix CIs were sent to be deleted and one nt CI was sent to be added.

 

7) Cmdb.dal.log. Depending on the log level set, this log will tell you what has been done and what will be done. It will show you the sql statements as well. If this log is in INFO mode, you will see only the sql statement but the actual value will be replaced by question marks for example something as: insert into .... [???????]. If you want to see the values that are being inserted, you will have to put this log info DEBUG mode.

 

😎 cmdb.operation.log. This log will contain pretty much everything related to uCMDB operations. This log contains the operation id of the operations. If you search for the operations id (some logs have operation id in Hexadecimal format while others have it in decimal format, so make sure you do the appropriate conversion) you can find all the entries in all the log files related to this operation.

"HP Support
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution."

Click the KUDOS star on the left to say 'Thanks'
Labels (1)
Tags (1)
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.