search

kieker-monitoring / kieker

Kieker's main repository
Apache License 2.0
70 stars 41 forks source link

[KIEKER-872] Sporadically, FS monitoring log files contain broken lines/records #1489

Open rju opened 1 week ago

rju commented 1 week ago

JIRA Issue: KIEKER-872 Sporadically, FS monitoring log files contain broken lines/records Original Reporter: Andre van Hoorn

Example:

...
$1;1324306211819225294;-1;frmAKTE.cmdClose_Click();AABBCCDD;3380;1324306211730506871;1324306211817769620;pc-avh;0;0
ate(..);AABBCCDD;3298;1324304683610428825;1324304683611519180;pc-avh;14;1
$1;1324304683616110152;-1;clsKlasse.adoPrimaryRS_WillChangeRecord(..);AABBCCDD;3298;1324304683613781074;1324304683614898723;pc-avh;15;1
...

The case study application was a VB6 program, running on Win 7. The Kieker4COM version was using Kieker 1.4. The monitoring log was located on a network share.

rju commented 1 week ago

author André van Hoorn -- Tue, 29 May 2012 14:49:55 +0200

It turned out that these lines are simply broken duplicates of lines already included in the file.

A frequent observation is also that the files include more lines than the configured maximum number of lines, e.g., 25000. In this case, each line >25000 can simply be removed. Duplicate lines appear also in the inner parts of the files, or at the end of the last file of a monitoring log, which is not filled completely.

Still, the assumption is that this is caused when writing to Windows shares, because we haven't observed this anywhere, so far.