[GH-ISSUE #512] [Feature]: Statistics and Archives #326

New issue

Open

opened 2026-05-07 00:08:54 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-07 00:08:54 +02:00

Owner

Originally created by @hollycroftlabs on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/512

Problem or Use Case

The statistics are a really useful part of the system, but the current implementation (using archives as the base) introduces some issues.

My archives are already using lots of storage, I print lots of the same item and I do not need the .3mf saving with each print - particularly when printing from the file manager (either directly or by the Queue system).
Reprinting from the archives means the statistics are not correct as the reprints are not logged in the archive.

Proposed Solution

I think there are two options:

Provide a user option that prevents the archive from storing the .3mf file - key information could still be stored and the file could be stored until print completion/failure (for filament usage calculations) but then deleted once completed.
Create a new "print log" that stores the relevant data from each print, time, weight etc but not the file. The archive can then be used for reprinting etc, but could be purged (on a user set schedule or manually) without affecting the statistics

Alternatives Considered

There is a setting called "Auto Archive Prints" - Im not sure what this option does. It seems to imply it will stop saving the 3mf file with the archive, but I am unsure.

Feature Category

Monitoring & Stats

Priority

Would improve my workflow

Mockups or Examples

No response

Contribution

I would be willing to help implement this feature

Checklist

I have searched existing issues to ensure this feature hasn't already been requested

Originally created by @hollycroftlabs on GitHub (Feb 24, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/512 ### Problem or Use Case The statistics are a really useful part of the system, but the current implementation (using archives as the base) introduces some issues. 1) My archives are already using lots of storage, I print lots of the same item and I do not need the .3mf saving with each print - particularly when printing from the file manager (either directly or by the Queue system). 2) Reprinting from the archives means the statistics are not correct as the reprints are not logged in the archive. ### Proposed Solution I think there are two options: 1) Provide a user option that prevents the archive from storing the .3mf file - key information could still be stored and the file could be stored until print completion/failure (for filament usage calculations) but then deleted once completed. 2) Create a new "print log" that stores the relevant data from each print, time, weight etc but not the file. The archive can then be used for reprinting etc, but could be purged (on a user set schedule or manually) without affecting the statistics ### Alternatives Considered There is a setting called "Auto Archive Prints" - Im not sure what this option does. It seems to imply it will stop saving the 3mf file with the archive, but I am unsure. ### Feature Category Monitoring & Stats ### Priority Would improve my workflow ### Mockups or Examples _No response_ ### Contribution - [ ] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested

BreizhHardware added the

enhancement

label

2026-05-07 00:08:54 +02:00

BreizhHardware commented

2026-05-07 00:08:54 +02:00

Author

Owner

@hollycroftlabs commented on GitHub (Feb 24, 2026):

You could also implement a link between the file manager and the archive - ie if a print originates from the file manager, then link to the file in the archive log rather than storing a separate copy

@hollycroftlabs commented on GitHub (Feb 24, 2026): You could also implement a link between the file manager and the archive - ie if a print originates from the file manager, then link to the file in the archive log rather than storing a separate copy

BreizhHardware referenced this issue

2026-05-07 00:15:25 +02:00

[PR #326] [MERGED] v0.1.9 #1001

BreizhHardware referenced this issue

2026-05-07 00:15:27 +02:00

[PR #331] [MERGED] Implement currency symbol handling and update related components #1006