delphi - What do you log in your desktop applications to improve stability? -
delphi - What do you log in your desktop applications to improve stability? -
i've started using smartinspect in delphi applications because users running bugs/problems couldn't reproduce on machine. when have general thought of problem i'll monitor application in few specific places confirm or not working.
when bug doesn't have obvious cause, sense lost. don't know start logging in order narrow downwards problem. there mutual techniques or best practices using logger?
smartinspect seems quite powerful, don't know quite log or how organise logs info meaningful , useful catching bugs.
note: i'm using smartinspect assume answers should suitable logging package.
here guidelines tried implement in my own opensource logging unit, it's generic, , state, should suitable logging package:
make several levels (we utilize sets) of logging, tune logging info needed; log exceptions, handled 1try...except block - , add together exception classes list not worth logging (e.g. econverterror) - e.g. our unit able log exceptions via global exception "hook" (no try..except add together in code), , handle list of exception classes ignored; log "fatal" errors, database connection issues, or wrong sql syntax - should done though "log exceptions" previous item; for such exceptions, log stack trace know calling context; be able log sql statements, or database access; add generic user interface logging, know main functions of software user did trigger (e.g. every toolbar button or menu items): it's mutual user said 'i have on screen/report, didn't anything'... , when see log, find "anything" done. ;) monitor main methods of application, , associated parameters; logging evolving feature: utilize general rules above, tune logging experiment, according debugging needs. delphi logging desktop-application
Comments
Post a Comment