Hello
Stéphane,
When
you use an Int64 column as ID column, Log4View treats this as a timestamp and converts it to 100 nanoseconds. That’s why you see this strange numbers.
You
should define the column like this:
ColumnName:
MyName
Key:
not checked
Parser
Type: Pattern
Pattern:
%property{MyName}
Let
me know if you need further help.
Mit
freundlichen Grüßen / Best regards
Ulrich
Proeller
PROSA
GmbH
Greinerstr.
23a
86316
Friedberg
Germany
Fon:
+49 821 450 610 81
Fax:
+49 821 450 610 82
Mobile:
+49 170 5417282
www.prosa-gmbh.de
[hidden email]
PROSA
Gesellschaft für System und Anwendungsentwicklung mbH
GF:
Ulrich Proeller, Ulrike Proeller
AG
Augsburg, HRB 17165
Ust.-Id.
Nr: DE202375536
Von:
stephane [via Log4View Support] [mailto:ml-node+[hidden email]]
Gesendet: Freitag, 14. Juni
2013 11:59
An: Ulrich Proeller
Betreff: Setting up a database receiver with extra columns
Hello,
I’m currently evaluating your log viewer.
My need is to monitor logs from a database via Log4Net (works the same way as Log4J).
I’ve tried to use a database receiver : it works fine for all columns provided in standard by Log4Net (level, thread, logger, ...) but my logs also include an extra column that I can’t map correctly.
This extra column is a long (Int64) and is used as a sequence (useful when the precision of the timestamps is too low). It’s correctly filled in the database (checked with
Sql Management Studio) but in your log viewer, it appears with a strange
format : 0.26, 0,27, 0,28, …
For now, I have the following settings :
ColumnName = Id
Key = checked (I want logs to be sorted by this id)
Parser Type : None
Pattern : not set
What’s wrong ? Does Log4View support extra long
columns ? If so, how can I configure the column ?
Best regards
Locked
