Logging, diagnostics and bug reports
#39.1What is logged
DBKraft writes five log files:
| File | Contents |
|---|---|
application.log | General application events. |
session.log | Connection sessions — start, end, user, engine, server version. |
error.log | Everything at Error level and above, mirrored here. |
performance.log | Timing records. |
debug.log | Verbose diagnostics. |
Each record is one line: Timestamp LEVEL SessionID Module Message.
🔒 Credentials are stripped from every record before it is written. Request logging records only the method, path, status and duration — never request bodies, because every request to the local service carries live database credentials.
#39.2Retention
Retention is per application session, not per day. Each time the local service starts, the previous run’s files are compressed to <name>-YYYYMMDD_HHmmss.log.gz and fresh files begin. The most recent previous session is kept.
This is deliberate: applications are usually restarted because something went wrong, and the report is filed from the next run. Discarding on startup would throw away exactly the logs the report exists to carry. There is no mid-session rotation, so a session’s records always stay in one file.
#39.3Crash dumps
Unhandled errors write a readable crash-*.dmp — a text report containing the exception chain, stack trace, thread, loaded modules, memory state, application version and OS details. It is a text file, not a native minidump, so it survives being e-mailed. Crash dumps are capped by count rather than deleted with the logs.
#39.4Reporting a bug
Help → Report a bug…
- Choose the kind of feedback (bug, idea, other).
- Describe what you did, what you expected, and what happened instead.
- Optionally add your email so support can reply.
- Attach diagnostic logs (on by default for bugs). The dialog lists exactly which files will be included and their sizes, warns you if crash reports are present, and tells you where the logs live and for how long they are kept.
- Include diagnostics adds a short environment block to the message body. Click what is included? to see it in full before sending.
- Press Send with logs.
DBKraft collects the logs, the crash dump, system information and version details into a ZIP named Logs_YYYYMMDD_HHMMSS.zip, and opens a pre-filled Outlook draft with the archive already attached.
Nothing is sent automatically. You review the draft and press Send yourself.
If Outlook is unavailable — or the draft opens but the file cannot be attached — DBKraft says so plainly rather than letting you send an empty report. It saves the ZIP, reveals it in Explorer, and opens your default mail client so you can attach the file by hand. The Show archive button reopens the folder.
For ideas and general feedback, no logs are collected; the report goes through a plain mail link, with Copy and Save as fallbacks.
🔒 A bug report never contains your host, port, service name, username, password, or any SQL you have written. Credentials are stripped from the logs before they are written, and no saved credential data enters the archive.
Reports are addressed to the DBKraft support team.