DX NetOps

  • Private Community

  • 1.  data in table ifstats_rate vertica database

    Broadcom Employee
    Posted Sep 12, 2017 03:41 AM

    Hi 

     

    have an issue witch data in table ifstats_rate vertica database. Previously can query for one year data but right now only left for one and half month.

     

    Even tried  to perform a full sync on DA data source but the result still same.

     

    eg1. select count * from ifstats_rate where tstamp

     

    Please advice

     

    Francis



  • 2.  Re: data in table ifstats_rate vertica database

    Broadcom Employee
    Posted Sep 13, 2017 01:43 AM

    Hello Francis,

    ***_rate tables carry the "as polled" date according to the data retention settings. Please check

    http://DAHOST:8581/rest/globalretentiondefinition 

    <PolledDataRetentionPeriod>

    If it has the default setting of 45 (days), your observation is expected behavior.

     

    Hth,

    Lutz.



  • 3.  Re: data in table ifstats_rate vertica database

    Broadcom Employee
    Posted Sep 19, 2017 12:18 AM

    HI Luts,

     

    Thanks for the update on this question.

    The output of provided the address shows 

    <PolledDataRetentionperiod>35</PolledDataRetentionperiod>

     

    Other period shows as :

    1. HistoricConfigurationDataRetentionPeriod =7

    2. GtdRollupDataRetentionPeriod = 730

    3. DailyRollupDataRetentionPeriod=365

    4. HourlyRollupDataRetentionPeriod =90

     

    Please advise how to change these Period.

     

    Regards

    Francis

     

     



  • 4.  Re: data in table ifstats_rate vertica database
    Best Answer

    Broadcom Employee
    Posted Sep 19, 2017 12:57 AM

    Hi Francis,

    you can change the retention settings using REST client. This is described here: Configure Data Retention Rates - CA Performance Management - 3.2 - CA Technologies Documentation  

    If you need to increase especially PolledDataRetentionperiod significantly, please validate the sizing. You can use the sizer to illustrate the impact of e.g. doubled period setting to the estimated data storage size.

    Hth,

    Lutz.