Configuring audit, snapshot and application options

Certain advanced audit, snapshot and application options can be configured using the Miscellaneous Settings page.

To set audit, snapshot and application options
  1. From the Appliance section of the Administration tab, select Miscellaneous.

    Field Name

    Details

    Allow Audit logs to be fully purged

    Users can purge the audit log of all events up to one month before the current date. This ensures that there is a minimum retention period of one month. You can configure the appliance to permit purging up to the current date. You can enable or disable full purging with this option. The default is No.

    Snapshot Disk Threshold

    The amount of disk space to reserve for the appliance snapshot. When the available disk space falls below this value, this is flagged on the Appliance Snapshot page.
    Select the one of the following values to use as the disk threshold:
    • 10%
    • 25%
    • 33% (default)
    • 50%
    • 66%
    • 75%

    Snapshot Migration Timeout

    You can set a maximum time for a snapshot migration to take. This is the migration timeout. If a snapshot migration takes in excess of migration timeout, it is considered to have failed and the migration aborts. Select the migration timeout from the following values in the list:
    • 5 minutes
    • 10 minutes (default)
    • 15 minutes
    • 30 minutes
    • 45 minutes
    • 1 hour

    History Compression Threshold

    The historical comparison pages 'compress' the raw history into changes. Entries are grouped by user and a sliding time threshold. This time threshold is necessary to enable you to view a number of separate changes made by Reasoning as a single change. Select from the following values in the list:
    • 15 seconds
    • 30 seconds
    • 1 minute (default)
    • 5 minutes
    • 10 minutes
    • 30 minutes
    • 1 hour
    • 8 hours
    • 24 hours
    The History Compression Threshold can be thought of as a sample rate. Select a value providing sufficient granularity to capture the change that you are looking for. For example, if a node is changing state every 20 minutes, a sample rate below this would be required to capture the changes, in this case, choose 10 minutes.

    Max number of visualizations to cache

    The maximum number of visualizations to cache. Select from the following values in the list:
    • 0 (default)
    • 10
    • 100
    Changing this setting requires a restart of the tideway service to take effect. Restarting the tideway service clears the visualizations from the cache.

    Time to cache visualizations for

    The time to cache visualizations for. This is the length of time from creation of the visualization rather than the last view. Select from the following values in the drop-down list:
    • 1 hour
    • 1 day
    • Forever (default)

Visualization cache

Complex visualizations which need to traverse over many relationships to build the data, such as the Application Dependencies - Software View, can be slow to load. Caching of generated visualizations has been introduced to ensure that this can be minimized.

You should note that cached data is not live, so using this feature will result in visualizations which may not be consistent with the current state of the datastore. This is particularly important when using the forever setting.

Changing either visualization cache settings requires a restart of the tideway service to take effect. Restarting the tideway service clears the visualizations from the cache.

Was this page helpful? Yes No Submitting... Thank you

Comments