This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
BMC Performance Assurance for Servers
TrueSight Capacity Optimization (Gateway Server) 20.02, 11.5, 11.3.01, 11.0, 10.7, 10.5, 10.3, 10.0 ; BMC Performance Assurance 9.5
On our TrueSight Capacity Optimization (TSCO) Gateway Server we have a number of manager runs with a 15 summarization interval and a Visualizer interval of 60 minutes. The environment has the Days in Advance collection requests enabled (the default configuration) so one can see three days of advanced collection requests scheduled in best1collect -Q output.
I am going to remove two nodes from a policy file and place those two into their own manager runs and policy file. In that manager run I will have a SPILL of 05 and a VIS_INTERVAL of 60.
Will the collectors scheduled three days out for these two nodes need to be stopped or unschedule before I schedule the new manager run?
TrueSight Capacity Optimization (Gateway Server) 20.02, 11.5, 11.3.01, 11.0, 10.7, 10.5, 10.3, 10.0
BMC Performance Assurance 9.5 and earlier
It would be necessary to clear the 'Days in Advance' collection requests before adding the machines to the new Manager run.
The reason is that the key used for the collection request on the remote node is:
- The agent data repository
- The start time directory
This means that once the Days In Advance collection request has been registered any new request that has the same Agent Data Repository and Start Time would be rejected as a duplicate of the existing request. Thus, changing things like the sample rate, summarization (spill) interval, end time of collection, or things like that would not be registered on the remote agent until the pre-registered Days In Advance collection requests were out of the agent *.als file.
The following command can be run to clear the collection request from the remote node:
You have to run the following command from the command line to clear the collection request on the remote node:
"%BEST1_COLLECT_HOME%\bgs\bin\best1collect.exe" -k -U SYSTEM -n <agent node> -b <begin time>
For example, to stop the collection request on remote node 'topgun' with a start date of 'Mar-16-2012.00.00' using the default agent data repository the command would be:
"%BEST1_COLLECT_HOME%\bgs\bin\best1collect.exe" -k -U SYSTEM -n topgun -b Mar-16-2012.00.00
For the TSCO Gateway Server on Linux the collection request can be cleared by running the following command as the TSCO Gateway Server Installation Owner:
$BEST1_HOME/bgs/scripts/best1collect -n [agent hostname] -b [date] -k
$BEST1_HOME/bgs/scripts/best1collect -n topgun -b Mar-16-2012.00.00 -k
Here are some data collection parameter changes that require the Days In Advance (COLREQ_DAYS_ADVANCE) collection requests to be cleared:
- The summarization interval
- The sample rate
- The Service Level (for example a change from 'Bronze' to 'Gold')
- The collection end time
- The metric groups to be collected associated with the Service Level defined in the Manager run
Any parameter that is not part of the collection request key on the remote agent would require the advance collection requests to be cleared before the change would take effect.
Q: What happens if I don't clear the days in advance collection requests after making a change?
The change will occur on the remote agent after the last existing 'Days In Advance' collection request has completed. So, if on March 16th there are already Days In Advance collection requests registered for March 17th, 18th, and 19th then a change made to Manager on March 16th wouldn't take effect until March 20th if the Days In Advance collection requests weren't manually cleared.Related Products:
- TrueSight Capacity Optimization
- BMC Performance Assurance