[GH-ISSUE #703] [Feature]: Add Printer Filter to Statistics Page #468

New issue

Open

opened 2026-05-07 00:10:31 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-07 00:10:31 +02:00

Owner

Originally created by @wreuel on GitHub (Mar 14, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/703

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

Bambuddy supports multi-printer setups, but the Statistics page currently displays farm-wide statistics only.

When managing multiple printers, it would be very helpful to view the same statistics scoped to a specific printer, instead of always seeing aggregated data across all printers.

For example, being able to quickly answer questions like:

How reliable is Printer A vs Printer B?
Which printer produces the most failures?
Which printer uses the most filament? (For the same item/print Printer A could have used more because of Purging)

Are time estimates more accurate on one printer than another?

Currently the only way to infer this is by using the per-printer widgets or external exports.

Proposed Solution

Add a printer selector/filter to the Statistics page.

The selector would contain:

All Printers (default – current behavior)
One option for each configured printer

When a printer is selected, all statistics on the page should update to show data for that printer only.

This should apply to widgets such as:

Quick Stats
Success Rate
Time Accuracy
Filament Types
Failure Analysis
Print Activity Calendar
Filament Trends
CSV/XLSX export

Suggested Implementation Approach

The filter should ideally be server-driven, rather than filtering client-side data.

A possible implementation would be to extend stats-related endpoints with an optional query parameter:

printer_id=<printer_id>

Example endpoints that could support this:

/archive-stats
/failure-analysis
/stats/export

This ensures:

Accurate results for large histories
No reliance on the frontend archive query limit
Consistent filtering across all widgets.

UI Suggestion

A simple dropdown in the Statistics page header would work well:

Printer: [ All Printers ▼ ]

Example options:
All Printers
X1C - Office
P1P - Workshop
A1 Mini

Why This Fits Bambuddy

Bambuddy already supports multi-printer environments, and the statistics system already contains per-printer aggregates such as:

prints_by_printer
time_accuracy_by_printer

This feature would make those capabilities more accessible and improve troubleshooting and performance analysis.

Alternatives Considered

No response

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 @wreuel on GitHub (Mar 14, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/703 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case Bambuddy supports multi-printer setups, but the Statistics page currently displays farm-wide statistics only. When managing multiple printers, it would be very helpful to view the same statistics scoped to a specific printer, instead of always seeing aggregated data across all printers. For example, being able to quickly answer questions like: - How reliable is Printer A vs Printer B? - Which printer produces the most failures? - Which printer uses the most filament? (For the same item/print Printer A could have used more because of Purging) Are time estimates more accurate on one printer than another? Currently the only way to infer this is by using the per-printer widgets or external exports. ### Proposed Solution Add a printer selector/filter to the Statistics page. The selector would contain: - All Printers (default – current behavior) - One option for each configured printer When a printer is selected, all statistics on the page should update to show data for that printer only. This should apply to widgets such as: - Quick Stats - Success Rate - Time Accuracy - Filament Types - Failure Analysis - Print Activity Calendar - Filament Trends - CSV/XLSX export # Suggested Implementation Approach The filter should ideally be server-driven, rather than filtering client-side data. A possible implementation would be to extend stats-related endpoints with an optional query parameter: printer_id=<printer_id> Example endpoints that could support this: /archive-stats /failure-analysis /stats/export This ensures: - Accurate results for large histories - No reliance on the frontend archive query limit - Consistent filtering across all widgets. # UI Suggestion A simple dropdown in the Statistics page header would work well: Printer: [ All Printers ▼ ] Example options: All Printers X1C - Office P1P - Workshop A1 Mini # Why This Fits Bambuddy Bambuddy already supports multi-printer environments, and the statistics system already contains per-printer aggregates such as: - prints_by_printer - time_accuracy_by_printer This feature would make those capabilities more accessible and improve troubleshooting and performance analysis. ### Alternatives Considered _No response_ ### 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