ItmSysp: Thinking ahead: Best practices for System p agents and Historical Data Collection
whisen 060000NG7K Visits (11756)
Chess players are often asked how many moves ahead they can see. While computers can calculate millions of positions a second, humans depend on strategy, experience, pattern matching and even intuition. Even so, in certain positions, the best chess players can see 15 or more moves ahead. And yet, when this question was posed to Jose Raul Capablanca, chess world champion from 1921-1927, he is reported to have replied, "Only one, but it is always the right one."
And in regard to IBM Tivoli Monitoring products, a little forethought and planning can go a long way. Here are a couple of articles to help you out. The first is a set of best practices specific to IBM Tivoli Monitoring for System p agents. It covers an overview of the agents, how to do some basic but important set up and configuration, plus some details on accounting, data collection and integration with Tivoli Application Dependency Discovery Manager. See System p Virtualization Best Practices.
The second is a great paper from Ben Stern on Historical Data Collection. This paper covers historical data collection best practices across all agents, giving examples for particular agents that can be extrapolated to others. The paper describes important considerations that help your environment run efficiently and provide the data you require. So, be sure to read Historical Collection Best Practices. You'll be glad you did!