This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
rootdir [2022/02/11 15:32] yves [Logging] |
rootdir [2022/02/11 16:06] yves [Integrity check] |
||
---|---|---|---|
Line 46: | Line 46: | ||
{{ ::access_log.png?nolink&400 |}} | {{ ::access_log.png?nolink&400 |}} | ||
- | |||
==== Logging ==== | ==== Logging ==== | ||
Line 54: | Line 53: | ||
You can monitor logs for several kinds of acivity: | You can monitor logs for several kinds of acivity: | ||
+ | {{ :rootdir_logs.png?direct&400 |}} | ||
- | ==== Audit trail ==== | + | === Audit trail === |
- | We have a separate blog entry on [[21cfr11|21 CFR pârt 11 compliance]]. | + | The audit trail tab conbines any operations that were performed on both root directory entries and underlaying mounting point entries. |
+ | {{ :rootdir_audit.png?direct&400 |}} | ||
+ | The presented information [[21_cfr_part_11|21 CFR pârt 11 compliant]]. | ||
+ | === Activity log === | ||
+ | |||
+ | In addition to an audit trail, an activity log is available that chronologically tell you which user has been accessing what slides in the root directory: | ||
+ | |||
+ | {{ :rootdir_activity.png?direct&400 |}} | ||
+ | |||
+ | === Elmah log === | ||
+ | |||
+ | [[https://elmah.github.io/|Elmah error logs]] are a standard way of capturing runtime errors in software. While these logs are not specific to root directories, they can help troubleshoot intermittent problems. Examples include: | ||
+ | * connection information is (temporarily) no longer correct | ||
+ | * a file format may have been modified by its vendor and now no longer renders correctly | ||
+ | |||
+ | {{ ::rootdir_elmah.png?direct&400 |}} | ||
==== Integrity check ==== | ==== Integrity check ==== | ||
- | If you suspect certain slides in a particular root directory are corrupt, you can run an integrity check on a particular folder by going to | + | Elmah logs work great for ad-hoc troubleshooting, but when problems persist over time, a more structured and proactive approach is warranted. |
+ | |||
+ | When you suspect certain slides in a particular root directory are corrupt, you can run an integrity check on a particular folder: | ||
+ | |||
+ | This attempts to read all slides in a folder and reports on the ones that fail. You should then [[format_troubleshoot|try to find out why such slides cannot be read]]. |