Actions
Feature #38280
closedmgr/dashboard: add DEBUG mode
Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
General
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
Add DEBUG flag to provide debug-friendly features for both back-end/front-end without (if possible) the need to restart either Ceph-Mgr, Cherrypy or even refreshing the front-end.
Expected changes in behaviour when DEBUG is enabled:- Increased verbosity to Ceph-Mgr logs (this should already happen if Mgr Module logger is correctly mapped to Ceph-Mgr log levels)
- Angular
enableProdMod
not active. (is it possible without JIT build?).- Ideas: serve 2 Angular builds (prod and dev) from different locations.
- Increase Broswer console verbosity and enable Angular Profiler (for
ng.profiler.timeChangeDetection()
profiling).
- Ceph command:
ceph dashboard debug true
- Back-end: switch cherrypy enviroment to
staging
(fromproduction
) (viacherrypy.config.update
) - Front-end: once debug is enabled, back-end might send
X-Debug: on
header (no need to do active polling). This has the benefit that no extra polling is required.
Updated by Ernesto Puerta about 4 years ago
- Is duplicate of Bug #41990: mgr/dashboard: hide Python tracebacks in response errors added
Updated by Ernesto Puerta about 4 years ago
- Status changed from New to Duplicate
Updated by Ernesto Puerta about 3 years ago
- Project changed from mgr to Dashboard
- Category changed from 132 to General
Actions