BugZero updated this defect 55 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
3/25/2024
Smart Assurance - Watch4Net/M&R
No affected releases provided.
No fixed releases provided.
Watch4net | ViPR SRM : Defining the retention period for each of the aggregatesHow to define the retention period for each of the aggregates in Watch4net | ViPR SRM
In the Watch4net | ViPR SRM config.xml file you can define the retention period for each of the aggregates. The config.xml is usually in the following location: UNIX/Linux: /opt/APG/Backends/APG-Backend/Default/conf/ Windows: C:\Program Files\APG\\Backend\APG-Backend\Default\conf\ You should review and edit this file based on your needs and on the space you can allocate to the database. For example, keeping 10 minutes aggregates for a very long period will create a huge database that will fill your disk in a short time and will affect APG performances. The name attribute of an aggregate refers to the aggregates defined in the aggregate definition file. config.xml <group name="group"> <!-- For each aggregate defined in the aggregates configuration file mentioned below, there should be one element here describing the span-time retention to use.The name attribute only stands here as an ID that references the aggregate defined in the aggregate definition file. --><raw><!-- 1 month retention --><span-time>2678400</span-time></raw>[]<aggregate name="1week"><!-- 7 years duration --><span-time>220752000</span-time></aggregate></group><!-- This element contains the location of the aggregates definition file. --><aggregates-definition>conf/aggregates.xml</aggregates-definition> AggregatesAs mentioned in the first comment of the file below [APG]/Backends/APG-Backend/Default/conf/aggregates.xml, it is better to keep this file as is to preserve data integrity. It is always possible to edit this file when you install APG, before starting to collect data. You can add or remove aggregation periods depending of your needs. Make sure you keep a backup of the original file before modifying it. Backup any custom configuration you made because this file can be modified when proceeding to an upgrade procedure. aggregates.xml <!-- *************************************************************************** * If you don't want to RUIN ALL YOUR DATA you should NOT TOUCH THIS FILE. * *************************************************************************** --><config> <!-- Real-time values. --> <raw> <!-- parts of 6 hours --> <split-period>21600</split-period> </raw> <!-- 10 minutes aggregate. --> <aggregate name="10min"> <!-- period: 10 minutes --> <period>600</period> <!-- parts of 6 hours --> <split-period>21600</split-period> </aggregate>[]</config>