abstract the input source?

[slestak]

Vinay,

I really like this interface.

Considering ways to make it able to ingest other sources of log data.
Particularly this source:

https://github.com/andreisavu/mongodb-log

Also wonder if the regex search field could be altered to also allow
searching by time, facility, etc. What do you think of a radio button
or a domain specific language?

[Vinay Sajip]

Sorry, I don't understand what you mean. Which exact interface are you
referring to?

Regards,

Vinay Sajip

[Steve Romanow]

I am saying right now you have a socket server interface only.

If the input to logview could be modularized, I could see potential
for reading a file off disk, maybe for the mongodb-log issuing a js
query to hit the mongo instance.

[Vinay Sajip]

Ok, I see - you were talking about liking the UI. Agreed that the
logging events interface is sockets only, but it would be fairly easy
to either adapt logview for your needs, or to set up some mechanisms
to get log data from wherever + send them to logview via a socket. The
reason I haven't built this kind of functionality into logview is that
it's just meant to be a basic viewer and not anything more
sophisticated, others can build on top of it to support MongoDB, Redis
etc. etc. if they need to. I want to keep the dependencies for logview
simple - Qt as essential and ZeroMQ as optional.

Regards,

Vinay Sajip

[Steve Romanow]

I think I will attempt that functionality. Instead of hard-coding
mine, I wanted to try to make it flexible enough to allow the input
source of the log messages to be configurable.

[Steve Romanow]

At the moment, I am using a webapp (graylog2) but would rather keep my
focus on python.