Mercurial > hg > orthanc
comparison TODO @ 4448:581d87e25536
todo
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Wed, 13 Jan 2021 18:48:53 +0100 |
parents | 330c4a4c103b |
children | a86fd55c4df0 |
comparison
equal
deleted
inserted
replaced
4447:8421b3fc02d7 | 4448:581d87e25536 |
---|---|
176 | 176 |
177 ==== | 177 ==== |
178 Misc | 178 Misc |
179 ==== | 179 ==== |
180 | 180 |
181 ------- | 181 ----------- |
182 Logging | 182 Performance |
183 ------- | 183 ----------- |
184 | 184 |
185 This is a wish expressed in issue #65 on BitBucket: | 185 * Check out rapidjson: https://github.com/miloyip/nativejson-benchmark |
186 | |
187 "Different levels for various modules (nice to have) | |
188 | |
189 We often need to debug DICOM interactions and logs are 'polluted' by | |
190 logs from the Rest API, i.e: since I have a process calling the | |
191 /changes route every 5 second, I'm lost in 17000 /changes record in my | |
192 logs everyday while I just want to check what kind of C-Find requests | |
193 are issued by a modality. If we go for it, logs could be configured | |
194 via the configuration file: i.e.: | |
195 | |
196 { | |
197 "Web": "info", | |
198 "Dicom": "debug", | |
199 "Db": "warning", | |
200 "WebViewer": "warning", // here WebViewer is a plugin | |
201 "Generic": "warning", // for all stuffs we could not port to the new logging API or old plugins .... | |
202 }" |