This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
TrueSight Capacity Optimization
CO all versions
What methods are available to obtain the TrueSight Capacity Optimization (TSCO) log files via the TSCO web UI and via the command line?
Check this video from the TrueSight Capacity Optimization Youtube channel: https://youtu.be/Ly_DfjilKfQ
Using the TrueSight Capacity Optimization (TSCO) Console
TSCO 9.0 and later
1. Access the TSCO Console with a browser via the standard TSCO URL.
If you cannot access the console because it is unavailable, use the command line LogGrabber script (see Using the command line).
2. Log in as a user with administrator privileges.
3. Navigate to Administration > System > Maintenance > Maintenance Activies tab
4. Click the Execute log Grabber button associated with the Log Grabber Maintenance Activity
6. In the Run: Log Grabber (Step 2 of 2: Hosts selection) screen select the BCO server(s) on which to run the log Grabber command. Click Proceed to execute the log Grabber activity. This will close the Run: Log Grabber screen and bring you back to the Maintenance Activites tab where the log Grabber task will now be in blue RUNNING state.
7. After a short time, click the word refresh in the "Processing may require some time, in order to know the current status please refresh this page." message at the top of the tab in the Info box. When the log Grabber task has moved from blue RUNNING to green FINISHED state move onto the next step.
- If you cannot get the logs from a particular machine, check that its scheduler is running. If it's not running, start it from the command line, connecting via ssh and issuing a ./cpit start scheduler from the BCO installation folder.
- If you cannot start the Scheduler, please use the command line LogGrabber script (see Using the command line).
8. Click the view deployment log button for the Log Grabber task.
9. In the Deployment Logs screen click the "Click to download the deployment log file" button for each of the current log Grabber executions (there will be one row per server selected in the Run: Log Grabber (Step 2 of 2: Hosts selection) screen with a current Execution Time in the table. You will get a browser's download prompt for a .pout file, that contains the collected logs.
10. Send the file(s) to Customer Support (see Sending files to BMC support).
- Log on the machines from which you need to gather data via ssh.
- Locate the BCO installation directory (for example /opt/bmc/BCO) and access the tools subfolder. or
- Run the script logGrabber.sh. This script creates a .tar.gz archive file containing the logs of all TSCO services installed on the local machine. This file will be created in the same directory as the logGrabber.sh script itself.
- Download the archive via scp, for example using WinSCP.
- Send the file(s) to Customer Support. See KA 000097282: Sending files to BMC support (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000097282)