[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [StrongED] Re: / Wimplog and styleguide
On 2017-01-17 16:10, Peter Young wrote:
Concerning Reporter in your other message, as someone who isn't at all
technically skilled I fond the set-up confusing, and going through the
myriad of lines of report that it produces rather tiresome. My fault,
not its.
Only in the sense that for some reason you felt you had to look at it.
Why?
The mainframes I used to work with produced central logs, in detail,
that
were millions of lines long, every single day. Nobody looked at them in
their entirety. When a specific problem required it, people would look
in
very great detail at tiny subsets of a single system's log, or (often)
the
logs of several related systems that had all been running at once.
The point though, is that to have it there to be looked at by anyone, it
has to be collected in detail all day, every day.
It's a long time since I ran a RO system for real, but when I did, I
arranged for the !Reporter logs, which are normally held only in RAM,
to be dumped to disk every few hours, and then stored for several
months.
I looked at them, when problems happened, and also to see what the
normal
pattern of use (perhaps at certain times of day, or around the startup
of
particular apps) was, to compare 'normal' with 'broken' behaviour
because
that's another thing. Much of what's in a !Reporter log may look like a
problem, but not be, but you have to know what's normal to be able to
tell that.
And several months of stored logs was sensible... because some things
only
happened once per month...
--
Jeremy Nicoll - my opinions are my own
--=20
To unsubscribe send a mail to StrongED+unsubscribe@xxxxxxxxxxxxxx
List archives at http://www.Torrens.org.uk/RO/StrongED/index.html