Hi Eliot, a very general remark (not really related to BaseX logs, but logs in general): I have practiced the following approach already a number of times, doing everything with BaseX, as it goes without saying, and it has always been very satisfying:

(1) Parse the log files into an XML representation, using regex etc. to transform the text into highly structured information

(2) Mindset: a log event is a thing with properties; a property has a name and a value; properties model: "event-type", "time", "msg", (a) generic-properties (like IP-address, user, ...), (b) event-type-specific properties (e.g. return-code) (b may be extracted from the msg)

(3) And then you can generate nice reports and also implement a powerful Online-Log-Query API (command-line or GUI)

(4) The event model can be extended iteratively - defining more event types, adding more event type specific properties

Kind regards,

Hans

Am Mittwoch, 10. August 2022 um 19:52:01 MESZ hat Eliot Kimber <eliot.kimber@servicenow.com> Folgendes geschrieben:

We have released version 1.0 of our Project Mirabel server to our internal users.

Now we need to know who’s using it, so time for log analysis.

I haven’t given any thought yet to what log analysis might mean. So wondering if there are any tips and tricks for analyzing the BaseX logs when using the BaseX HTTP server.

Note that we don’t yet have users implemented, so we’re just looking at HTTP requests with different IP addresses.

Thanks,

_____________________________________________

Eliot Kimber

Sr Staff Content Engineer

O: 512 554 9368

M: 512 554 9368

servicenow.com

LinkedIn | Twitter | YouTube | Facebook