Log track of entities saturation and in case the MaxItem is reached

In B12 when the Max Item saturation is reached, Board gives no alert even if Data Readers fails to load data due to the impossibility to add new members.
It would be nice to have this error and also to have it tracked in the logs (such as Data reader failure etc).
Also having the saturation information monitored in some log would be helpful for the construction of reports that quickly advise the admin users in case of critical saturation levels.
Thanks

Find more posts tagged with

Accepted

Status: Accepted

Comments

Anastasia Pesyakova

Agree, admins should be alerted when critical saturation levels reached. It will help to avoid additional maintenance and db corruption. Pop-ups or email notifications can be introduced. Thanks!

Björn Reuber

Hello,

please keep in mind, that this is already logged in Diagnostic level (as Warning)

2023-04-04 10:15:22.391 +02:00 WARN br 655353ac-9571-4043-bc31-b14598ec4467 DataRead b041ec7c-4787-4325-aa43-8918607cbba9 2. ASCII Data Read Echo {"Record":10, "Row":"C04560\tA F BLAKEMORES CASH & CARRY", "Error":"Error : MaxItemNr exceeded on column 1 [C04560]"} Invalid row.

regards

Björn

Michael Williams

If you want a way for your Admin to be more easily alerted to the DataReader failure rather than checking the logs, you could try importing the log information into a Board cube and having a data load check screen to review.

Daniele Di Lorenzo

ok, but this require an implementation and could be not immediate. This type of errors should be immediatly notified with a push alert since the impact in the process and data reliability is relevant

Product Management Team

Hi Nicola, thank you for sharing your idea! We appreciate the time and effort you put into crafting your suggestion, and we understand the need of this solution. We have accepted this Idea to be part of our backlog and we are evaluating the feasibility of adding it to the development roadmap.

We are committed to delivering the best possible experience to our customers, and we must prioritize the features and enhancements that will have the most significant impact on your daily use of our software.