Log Management and Support Submission

Objective

The goal is to transform a monolithic and fragile log storage system into a reliable, organized, and autonomous one: daily folders replace the single text file to prevent any lock-up, configurable automatic cleanup preserves disk space, and one-click manual submission to support eliminates unnecessary back-and-forth — with full automated error reporting planned for a future phase.

1. Log Storage Structure

Application events are no longer recorded in a single text file. They are now distributed across distinct folders, named by day and prefixed with lg_.

Example folder structure on your machine:
📁 Logs
 └── 📁 lg_2026-05-17
      ├── app.log
      └── error.log
 └── 📁 lg_2026-05-16
      └── ...

Benefits of this structure

Benefit	Detail

Benefit	Detail
Reliability	No more lock-ups due to the size or line count of a single file.
Clarity	Instantly find events for a specific date by opening the corresponding folder.
Efficiency	Support can quickly target the relevant period during diagnosis.

2. Automatic Log Cleanup

To prevent your disk space from filling up, an automatic cleanup mechanism is built in.

Default behavior

Each log folder is kept for 7 days, then automatically deleted.
This number of days is adjustable to suit your needs.

How to adjust the retention period

Open the Configuration window in CienApps.
Go to the Logs tab.
Adjust the number of days as preferred.

💡 Tip: If you are tracking a recurring issue with support, you can temporarily increase retention to 15 or 30 days to keep a broader history.

3. Send Logs to Support

To simplify communication with our technical team and speed up ticket resolution, a new action has been added to the Help menu.

How to proceed

Open the Help menu in CienApps.
Click the Send logs to support option.

What this action does

Step	Automatic Action

Step	Automatic Action
1	The system gathers log folders from the last N days (`lg_YYYY-MM-DD`).
2	It compresses everything into a ZIP archive.
3	It generates a pre-filled email with your environment details.
4	The email is sent to support with the attachment.

By default, logs from the last 2 days are included. This number is configurable from the Logs tab in the Configuration window.

Email structure:

Table

Element	Description

Element	Description
Subject	Prefix `[LOGS]` + company name + user identifier + precise timestamp down to the second. Allows support to immediately identify the source and time of submission.
Sender	Email address configured in the application.
Attachment	ZIP archive named following the format `logs_[COMPANY]_[DATE]_[TIME].zip`.
Body	Structured block indicating the company, user, application version, submission date, attachment name, and covered period (number of days included).

✅ Result: Support instantly has all necessary information to analyze your ticket without prior exchange.

4. Next Evolution (Phase 2)

This feature constitutes Phase 1 of the project. In a next step, the system will be able to trigger automatic submission of relevant logs directly after an error occurs or upon specific support request. You will retain the ability to enable or disable this automation from the Logs tab in the Configuration window.