Comments (1)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 jalvord commented Permalink

Another important choice is whether to collect historical data on the TEMA or Agent side or on the TEMS. TEMA is speedier - writing to a local file instead of many RPC [Remote Procedure Calls] to the TEMS through the network. TEMA keeps on recording data even if the TEMS is down or communication goes out for a while. On the other hand, it does consume local disk storage at every agent. If something goes wrong, the historical data can collect "forever" and leave you with a full mount point or disk and a broken agent. That can be managed with an environment variable like this at the agent. <div>&nbsp;</div> KHD_TOTAL_HIST_MAXSIZE=5 <div>&nbsp;</div> It doesn't actually stop at 5 megs, but it will not start a new collection if beyond that limit. <div>&nbsp;</div> The biggest mistake people make is to collect "everything" - like Unix Process [200-400] every 5 minutes. That will eat your database out of house and home. I once worked with a customer who wasn't paying attention. The short term historical data collected at the TEMS and there was so much data that the total was 200 gigabytes behind and falling more behind 5 gigs each day. In the end the IBM MQ Agent experts told him it was nonsense to collect so much data and he just stopped. <div>&nbsp;</div> You should justify the need for historical data and not just blindly say "everything". <div>&nbsp;</div> John Alvord, IBM Corporation