You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While browsing on my app, I usually glance at the debugbar to see if my memory usage and request duration is within my normal limits.
It would be great to have a configuration setting in config/debugbar.php that sets a memory_usage_warning_threshold (in kilobytes) and a request_duration_warning_threshold (in milliseconds).
If the memory usage/request duration then exeeds this threshold, the memory usage/request duration block in the debugbar lights up, something like this;
This way, I can quickly see something's wrong without having actually having to look at the values themselves.
The text was updated successfully, but these errors were encountered:
peterjaap
changed the title
Feature request: configurable threshold for clearer warnings
Feature request: configurable threshold for indicator warnings
Jun 10, 2020
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If this issue is still present on the latest version of this library on supported Laravel versions, please let us know by replying to this issue so we can investigate further.
Thank you for your contribution! Apologies for any delayed response on our side.
While browsing on my app, I usually glance at the debugbar to see if my memory usage and request duration is within my normal limits.
It would be great to have a configuration setting in
config/debugbar.php
that sets amemory_usage_warning_threshold
(in kilobytes) and arequest_duration_warning_threshold
(in milliseconds).If the memory usage/request duration then exeeds this threshold, the memory usage/request duration block in the debugbar lights up, something like this;
This way, I can quickly see something's wrong without having actually having to look at the values themselves.
The text was updated successfully, but these errors were encountered: