Russian Tivoli User Group

Expand all | Collapse all

Tivoli Monitoring history configuration

  • 1.  Tivoli Monitoring history configuration

    Posted Fri August 13, 2021 02:54 PM

    Hello, Colleagues. We encounter history collection issues. To be exact we are talking about YN agent, and history collection interruption which usually goes with /opt/IBM catalog disk space overfill.

    Previously we opened PMR regarding the issue, but no luck other than recommendation to set KHD_TOTAL_HIST_MAXSIZE_MB,KHD_HISTSIZE_EVAL_INTERVAL_SEC.

    Also we were notified, that there is a limit for hist files, and if its size goes over the limit, then hist collection interrupts, and hist will still be collecting within hist files, but will not go to Warehouse.

     

     

    /opt/IBM catalog usually has size 4GB

    Could you please give recommendations for values to set KHD_TOTAL_HIST_MAXSIZE_MB,KHD_HISTSIZE_EVAL_INTERVAL_SEC so thet 4 GB of /opt/IBM would be enough for YN agent with its logs and hist files and its size did not go over the limit, which can handle proxy agent? We suppose, that hist files in our environment does not go over 2GB while it works well.

     

    Thanks a lot



    ------------------------------
    Dmitriy Zinovyev
    ------------------------------


  • 2.  RE: Tivoli Monitoring history configuration

    Posted Sun August 22, 2021 07:06 AM

    If you exceed KHD_TOTAL_HIST_MAXSIZE_MB - before a collection interval - there is no historical data collection performed at all. Storage size can be exceeded since it is only checked at the start of each collection. That needs to be prevented....

    This document shows how to detect agent side issues

    Sitworld: Discovering Historical Data Export Problems at Agent
    http://itm-sitworld.blog/2017/04/04/sitworld-discovering-historical-data-export-problems-at-agent/

    or 100+ errors anyway.

    Each STH file can contain as much as 48 hours of data, assuming export is once a day. But you can export more often... if export every hour STH file will contain 24-25 hours of data.

    Not quite sure what  "opt/IBM catalog usually has size 4GB" means

    Guessing that df /opt/IBM is 4 megs or so

    A lot of it depends on how big the STH files are normally... that is almost entirely user controlled... what attribute groups to collect, how often, how often to export data.

    Sometime customers control where historical data is kept, in some other file system using this environment control [example]

    CTIRA_HIST_DIR=/itm/hist

    You can also control logs that way

    CTIRA_LOG_PATH=/itm/logs
    =======================================
    In my experience it is very easy to get more historical data that expected in ITCAM agents. Much of the data records information about connections and interactions. As the workload goes up, the STH amount of data goes up and storage estimates that were accurate 2-3 years ago is way to small and you started using more disk space than expected.

    John Alvord
    Advisory Engineer and ITM 6 Historian








    ------------------------------
    JOHN Alvord
    ------------------------------