Technical Tip: Fortianalyzer command execution 'diagnose fortilogd logvol-adom' output shows wrong values.

Description

This article describes the solution to resolving the problem with the command execution that should display the log volume per ADOM but returns the wrong values. 

diagnose fortilogd logvol-adom

Scope

FortiAnalyzer v7.6.0 to v7.6.6.

Solution

In versions 7.6.0 to 7.6.6, when the FortiAnalyzer is required to validate the log volume received per ADOM, execute the following command:

diagnose fortilogd logvol-adom

The output displays incorrect values, which causes some problems in estimating the storage needed for the ADOM to comply with the retention policy.

To resolve this problem, it is now possible in version 7.6.7 that the process is performed correctly and obtains the correct value.
This is published in the release notes (1217641).

Related documentation:

• Resolved issues

• Technical Tip: How to estimate disk space needed for Archive and Analytics logs

• fortilogd