Welcome to the BrightGauge Enhancement Forums

Currently, if you export in CSV multi-layered gauge, it renders CVS file with the accurate number of columns, however, the manes are not preserved so you need to basically reconcile which column in the sheet matches the gauges. The order of the columns is also is not preserved, so if you wan to use the data in CVS, you firs need to do thorough reconciliation.  

Summary:
Requesting a native integration between Cove Data Protection and BrightGauge to enable direct reporting and dashboarding of backup metrics within BrightGauge.

Business Need:
As an MSP, centralized reporting is critical for proactive monitoring, SLA tracking, and executive-level visibility.

Requested Functionality:

• API-based data sync between Cove and BrightGauge

• Visibility into backup status (success/failure), last backup time, and device health

• Storage utilization and growth reporting

• Alerting metrics for failed or overdue backups

• Client-level and global reporting support

Currently if you have scheduled reports using a report template, and then make changes to the template, those changes are not reflected next time the scheduled report runs.

The only way to update the scheduled report is to start from scratch and schedule a new report using the updated template.

Have the ability within a scheduled report config to revert/reset the layout to the active template would be a massive time saver.

I would like the ability to have a gauge that would show which/how many servers have blocked patches. As we get into a more security focused world, some of our clients would like to know what servers did not have patches applied due to being blocked.

As well as having a pdf options, have the ability to export the report as a CSV. This will allow those of us who want to do granular reporting utilize items such as PowerBI to graph and trend this over and beyond the 240 days available in brightgauge.

It would be very beneficial to be able to report on the team members that are receiving project surveys-  similar to the way that you can report on this from a CSAT perspective. 

Please change the DataSource LogicMonitor - DataSet Device Alerts sync frequency to something much quicker than 4 hours.

30 minutes would be the max that it should refresh. 

A gauge of alerts needs to be more "real-time".

Allow for scheduled reports' email FROM address to be configured rather than just noreply@brightgauge.com

We would like to configure some reports to go directly to end customers but do not consider it very professional looking if they come from the brightgauge domain.

Ideally this would allow for sending from our domain - obviously on condition that the correct DNS records are in place

In the Patch Management section, there are two columns: Failure Date and Installation Date. I’d like to propose the following enhancements:

The Success Gauge should reflect only the latest successful installation date, rather than listing repeated entries.
The Failure Gauge should similarly show only the most recent failure, even if the machine is offline or hasn't updated since.
This would make the gauges more meaningful and reduce clutter from repeated or stale data.

Please make dataset sync frequency adjustable. Syncing a dataset of alerts every 24 hours is not useful.

ex. LogicMonitor -Device Alerts for the past 30 Days