I suggest the "the nerd" strategy.
The ostrich doesn't need logs. In case something goes wrong, the ostrich prefers to not know, because that way, he is quasi innocent, because he "didn't know". Of course in court this doesn't really matter, as the admin is responsible for any disturbance his system may cause. To avoid unnecessary breakdowns, an admin has to keep himself informed. The ostrich ignores that.
- ignorance is bliss and has to be met with leniency
The beginner logs to impress his friends and gain prestige in the community. Without much thinking he logs a lot.
- log everything, use
loggerto arbitrarily produce even more logs
- do not distinguish between useful or not, read all logs and post stuff them online
- after a while, stop reading your logs at all (too much to read…)
- do not know, what exactly the logs mean
- ignore the law, don't mind the privacy of other users your logs may breach
- do not inform, that you log, what you log and for how long logs are being kept, because it is a secret (ye know, for security reasons)
- make logs accessible to everyone, especially to people they do not concern (necessary breach of security to impress people in the forum)
It may look like certain people would like to introduce this strategy for logging every Internet activity in Germany. But that cannot be, as this would be stupid.
The nerd knows a little about the possibilities of the programs running on the system(s). So, during normal service he creates logs
- to WARN and reads this logs regularly
- log messages that might prove useful to be able to reconstruct things. and reads them only when needed
- he acts as Datenschutzbeauftragter and informs other users (whom it may concern) of the fact
- that logs are being created and stored
- how long logs are being stored
- who has access to the logs
Only during debug sessions he
- logs everything
Pretty much the same as the nerd, but the profi gets paid for solving breakage fast. Some get important LOG warning per SMS or per pager. Day and night. Yay.
doc/howto/log.strategies.txt · Last modified: 2011/02/05 12:44 by orca