Mantis Bugtracker
  

Viewing Issue Advanced Details Jump to Notes ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0000114 [Software] Logging feature always 13-08-10 15:32 14-10-10 23:27
Reporter Peter View Status public  
Assigned To Peter
Priority normal Resolution fixed Platform
Status closed   OS
Projection none   OS Version
ETA none Fixed in Version 1.3.5 Product Version 1.3.5
  Product Build
Summary 0000114: provide minimum log update functionality
Description now this might have to be how many packets are logged out of all possible ones, rather than a given rate. e.g. if we were to specify log no more often than once every 100ms, we might get 2 packets together then skip one, etc, so the data wouldnt have consistent gaps between it.

so may be better to specify how many packets are not logged between each that is. e.g. 0 = all logged, 1 = 50% logged, 2 = 33% logged, 3 = 25% logged, 4 = 20% logged, etc.

not the most easy thing to convey to users, but most accurate way to not record all data.
Steps To Reproduce
Additional Information
Attached Files

- Relationships

- Notes
(0000110)
Peter
14-10-10 23:27

this is in v1.3.5 but as a ini option only (LogDivider). 0 = 100% of normal log data logged, 1 = 50%, 2 = 33%, etc.
 

- Issue History
Date Modified Username Field Change
13-08-10 15:32 Peter New Issue
13-08-10 15:32 Peter Status new => assigned
13-08-10 15:32 Peter Assigned To  => Peter
14-10-10 23:27 Peter Note Added: 0000110
14-10-10 23:27 Peter Status assigned => closed
14-10-10 23:27 Peter Resolution open => fixed
14-10-10 23:27 Peter Fixed in Version  => 1.3.5


Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
36 total queries executed.
30 unique queries executed.
Powered by Mantis Bugtracker