| Title | Not enough logging control |
| Status | closed |
| Priority | essential |
| Assigned user | Gareth Rees |
| Organization | Ravenbrook |
| Description | There's only one level of logging at the moment. This makes it difficult to get detailed information from a user when analyzing a bug or a support request. |
| Analysis | We should log a great deal more stuff than we do, but have a minimum log level in the configuration. That will make testing much easier (you just turn up the log rather than adding verbose instructions to the code like we did today). |
| How found | manual_test |
| Evidence | <http://www.ravenbrook.com/project/p4dti/doc/2000-10-26/perforce-alpha-test/> item 20 |
| Observed in | 0.3.2 |
| Created by | Richard Brooksby |
| Created on | 2000-11-22 14:37:39 |
| Last modified by | Gareth Rees |
| Last modified on | 2001-12-10 19:02:52 |
| History | 2000-11-22 RB Created from sources (see evidence). |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 9874 | closed | 2001-03-13 10:38:39 | Gareth Rees | Added log_level configuration parameter, which gives the minimum priority level of message to appear in the replicator's log. Removed verbose configuration parameter, which is now redundant. |
| 6030 | open | 2000-12-15 13:21:33 | Nick Barnes | Verbosity control for Teamtrack integration, and in AG. |
| 6027 | open | 2000-12-15 13:01:54 | Nick Barnes | Verbosity control. |