comparison TODO @ 3673:3e68c3b4e3df storage-commitment

integration mainline->storage-commitment
author Sebastien Jodogne <s.jodogne@gmail.com>
date Fri, 14 Feb 2020 17:55:53 +0100
parents ea8c1c0e81eb
children 5b731d898bee
comparison
equal deleted inserted replaced
3670:e64432336055 3673:3e68c3b4e3df
191 External applications 191 External applications
192 ===================== 192 =====================
193 193
194 * Create REST bindings with Slicer 194 * Create REST bindings with Slicer
195 * Create REST bindings with Horos/OsiriX 195 * Create REST bindings with Horos/OsiriX
196
197
198 ====
199 Misc
200 ====
201
202 -------
203 Logging
204 -------
205
206 This is a wish expressed in issue #65 on BitBucket:
207
208 "Different levels for various modules (nice to have)
209
210 We often need to debug DICOM interactions and logs are 'polluted' by
211 logs from the Rest API, i.e: since I have a process calling the
212 /changes route every 5 second, I'm lost in 17000 /changes record in my
213 logs everyday while I just want to check what kind of C-Find requests
214 are issued by a modality. If we go for it, logs could be configured
215 via the configuration file: i.e.:
216
217 {
218 "Web": "info",
219 "Dicom": "debug",
220 "Db": "warning",
221 "WebViewer": "warning", // here WebViewer is a plugin
222 "Generic": "warning", // for all stuffs we could not port to the new logging API or old plugins ....
223 }"