Monitoring, Version 6.2
Installing Tivoli Universal Agent applications is almost impossible to estimate because of the varied nature of what the Tivoli Universal Agent can monitor. If you are using user-provided scripts, for instance, then you can create an application in half an hour. If you have to create your own scripts then that can take days depending on your skill level with scripting and the complexity of the script. Likewise, log file monitoring can be straightforward or complex depending on the format of the log file.
Adjust the time estimates on a case-by-case basis. Be very careful in moving metafiles from development and test to production because of the versioning nature of the Tivoli Universal Agent. Depending on how they are implemented, changes to the metrics being collected can cause the version of Tivoli Universal Agent to increment, resulting in loss of all customization done to the Tivoli Universal Agent.
Make sure that all the desired metrics are added to metafile and maybe two or three placeholder generic metrics can be added to accommodate future modifications without needing a version change. Another option is to use two very generic metrics such as MetricName and MetricValue and write situations such as scan for string with in a string to catch the data. When the metafiles are imported, make sure the Tivoli Universal Agent is connected to the hub monitoring server first and then later it can be moved to any desire remote monitoring server.
[ Top of Page | Previous Page | Next Page | Contents | Index ]