Reports, backup, audit and operations

Reports

In Reports select:

• report type;
• project/repository scope;
• date range;
• day, week or month grouping;
• language;
• export format;
• whether detailed changed paths should be included.

Main types include:

• repository evolution;
• portfolio overview;
• operations/administrative report.

The reporting module may require a license. Export artifacts are temporary and can be downloaded only by their owner or a system administrator.

Backup

In Backup / Restore configure:

• backup root;
• number of full backups to retain;
• verification after completion;
• mandatory restore validation before deleting old chains.

A full backup must protect PostgreSQL metadata and Vault Storage as one verifiable set.

Example reason:

Before upgrading from 0.1.3 to 0.1.4

Restore validation

Do not accept a backup merely because a file exists. Verify manifest/checksums and perform restore validation in a controlled environment.

Audit trail

The Audit page can be searched by:

• operation;
• target;
• actor;
• correlation ID;
• severity/result.

A correlation ID links the user-visible error, API request and technical event.

Operations

Operations is the official WEB/Admin center for production actions:

• health checks;
• acceptance/workflow tests;
• safe package repair;
• host-state archive;
• artifact build and download when the machine is a build host;
• controlled deactivation/reinstallation preparation.

Long-running actions are executed by the protected operations agent and show stage, progress and a bounded log.

Build targets

A build host may show targets for:

• Server RPM/payload;
• Linux RPM/DEB client;
• Windows x64 client on a native Windows host;
• release bundle.

The SQL gate is mandatory and must not be disabled. A failed build must not be published as a successful release.

System

The System page shows runtime identity, modules/capabilities, component health and personal UI preferences.