The log artifact is a new feature in RSA Identity Governance and Lifecycle Version 7.1.1 that will aide in the gathering of log information in the event that a support ticket is created. It is an administrator-only feature that can gather the most widely used log files when troubleshooting problems in the application, thereby reducing the time to identify the root cause of an issue. It is designed to work on a node-by-node basis and will work for different architectures such as Hard Appliance, Software Bundle with remote database, and Clusters, along with the different application servers we support. The page can be found under the Admin > Diagnostics menu.
It is located on the Log Artifact tab.
The following is a description of the different areas of the page:
- Node Name - This tells the user which machine the user is current logged into. This is important because the utility will gather all the log files that are local to that node. If you are in a clustered environment and need logs from all the nodes in the cluster you will have to log into each one individually and gather from each node. The information after the ‘:’ is the node type for the machine. There are two types Systems Operation Node (SON) and General. Log files should be collected from all nodes if this is a cluster. At a minimum they should be collected from the SON.
- Date Range - This can limit the amount of information that is extracted from the log files. For instance if the problem is two days old you would want to limit the log file from the last few days. The default of 30 days will typically be sufficient.
- Create File Password (Optional) - This will allow you to password protect the zip file.
- Generate Zip File - This button is what will start the gathering of all the logs and then zipping of them into a single file.
- Current Status - After initiating the gathering process, this area of the page will display the status of what is being gathered. It is not refreshed automatically so to see any new status you will need to refresh the page manually. Once it is complete it will display the file that is available from this node.
- Download - This button will be enabled once the gathering/zipping process is complete. It will allow you to download the most recent process.
When in progress the Current Status will contain the current step.
Once completed the zip file will be available for download
Upon completion of the process the status section will show the pertinent information about what was chosen for this invocation. As detailed in the picture we will store the zipped file on the server and it will stay there until the next invocation of the process. To store the file locally just press the Download button.
- When gathering log files for nodes in a cluster the Administrator must log into each node and run the process. We only gather the local files to the server.
- Warning messages from the tool does not indicate a problem with the feature. Not all environments/configurations will contain the same log files. The Warning messages are primarily for Engineering.
- The gathering of the logs for a remote AFX server is still a manual process.
- The gathering of logs for a remote database is also a manual process. We will display a Warning message with this configuration as the database logs will not be local.
- Some log files may reside in different directories depending on a customer’s configuration. We will make a best attempt to find them with some well-known locations. If we can’t find them we will display a Warning message to that effect.
- The process does not gather an AWR.
- The process does not maintain previous ZIP files. At the start of a new generation the previous file will be removed, this will reduce the chance of running out of disk space.
See the following video which demonstrates the use of the feature.