If used for, problem resolution, historical information & periodic
reporting, etc. this is essentially a low-use log and you could log a
lot of information using almost any logging facility.
If, however, management wants immediate access to the logs for status
monitoring, use analysis, etc. This is a high-use log and I would
consider logging everything to a separate log database. (maybe on a
separate db server).
The db approach allows maximum flexibility and surprising little
logging overhead (most of the activity will be inserts).
I developed a system for one client that would log each time a record
appeared in a drill-down of search-results, and when a record was
selected for review. This system only logged counts (updated the log
records) but was surprisingly efficient.
Finally, it is likely that the next major versions of OSes will have
the native file systems based on databases -- so you will be ahead of
the game.
HTH
Dick
On Apr 21, 2004, at 6:48 AM, Claremont, Timothy wrote:
> I am writing an intranet app in a medical environment. As such, I
> need/want to track accesses to the data, client records, etc.
>
> What I am wondering is what is the most effective logging from both a
> security persepctive and a performance angle. Management sees the need
> to log as much activity as possible. This would mean logging the
> username (obtained with CGI variables), the date, the time, the page
> visited, as well as variables such as ClientNumber or ClientName to
> know
> whose record was viewed, etc. Also, was the record modified on this
> visit, WHAT was modified, etc. etc.
>
> As much as I would like a textbook answer, any references to case
> studies, etc would be appreciated!
>
> Tim
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
