Controlling the size of the performance database

Ops Center Analyzer Detail View User Guide

Version
11.0.x
Audience
anonymous
Part Number
MK-99ANA007-06
ft:lastEdition
2026-03-16

You can control the size of the performance database by setting values in the /usr/local/megha/conf/sys/app.db.purge.properties file.

The database purging activity is scheduled daily at 00:00 UTC. However, the purging activity starts only when the Analyzer detail view server is not performing any of the following operations:
  • REST API requests
  • Data batch importing
  • UI activities that require database access
Note: While purging activity is in progress, you cannot access the database.

You must set the following property to true when enabling purging activity:

app.db.purging.enabled

In addtion, you must set one of the following properties:
  • Time (app.db.time.based.purging.limit)
  • Size (app.db.size.based.purging.limit.in.gb)
  • Disk free space (app.disk.freespace.size.based.purging.limit.in.gb)

If you set more than one property, then only the highest configured criteria will be applied and further criteria will be skipped. The Disk free space purging is the highest priority. Size purging is a higher priority than Time.

  1. Log on to the Analyzer detail view server through an SSH client (like putty) as a root user.
  2. Type the following properties file path:
    /usr/local/megha/conf/sys/app.db.purge.properties
  3. Set the values according to the settings described in the following table.
    Parameter Values Description

    app.db.purging.enabled

    true, false

    Default: false

    Enable or disable database purging.

    app.db.time.based.purging.limit

    nD (days, Min: 7, Max: 3650)

    nM (months, Min: 1, Max: 120)

    nY (years, Min:1, Max: 10)

    Purge based on database age (days, months, or years). Example:

    app.db.time.based.purging=10M

    Saves the last 10 months of data.

    app.db.size.based.purging.limit.in.gb

    Min: 50

    Max: 10240

    Purge based on the database size (in GB). Deletes oldest folders in perf until the database size limit is reached. Example:

    app.db.size.based.purging.limit.in.gb=100

    Deletes the oldest folders until the database size is less than or equal to 100 GB.

    app.disk.freespace.size.based.purging.limit.in.gb

    Min: 10

    Max: 100

    Purge database based on the amount of free disk space available (in GB). Deletes the oldest folders in perf until the free disk space limit is reached. Example:

    app.disk.freespace.size.based.purging.limit.in.gb=20

    Deletes the oldest folders until the amount of free disk space is less than or equal to 20 GB.

    Note: If you make any change in the property file, then you must restart the Analyzer detail view server. If you type an incorrect value in the property file, then the Analyzer detail view server does not restart. The Analyzer detail view server updates the importStatus.properties file after the database purge operation and lists the correct data availability.