What are good NoSQL and non-relational database solutions for audit/logging database
Posted
by Juha Syrjälä
on Stack Overflow
See other posts from Stack Overflow
or by Juha Syrjälä
Published on 2010-05-05T14:59:16Z
Indexed on
2010/05/06
11:28 UTC
Read the original article
Hit count: 563
What would be suitable database for following? I am especially interested about your experiences with non-relational NoSQL systems. Are they any good for this kind of usage, which system you have used and would recommend, or should I go with normal relational database (DB2)?
I need to gather audit trail/logging type information from bunch of sources to a centralized server where I could generate reports efficiently and examine what is happening in the system.
Typically a audit/logging event would consist always of some mandatory fields, for example
- globally unique id (some how generated by program that generated this event)
- timestamp
- event type (i.e. user logged in, error happened etc)
- some information about source (server1, server2)
Additionally the event could contain 0-N key-value pairs, where value might be up to few kilobytes of text.
- It must run on Linux server
- It should work with high amount of data (100GB for example)
- it should support some kind of efficient full text search
- It should allow concurrent reading and writing
- It should be flexible to add new event types and add/remove key-value pairs to new events. Flexible=no changes should be required to database schema, application generating the events can just add new event types/new fields as needed.
- it should be efficient to make queries against database. For reporting and exploring what happened. For example:
- How many events with type=X occurred in some time period.
- Get all events where field A has value Y.
- Get all events with type X and field A has value 1 and field B is not 2 and event occurred in last 24h
© Stack Overflow or respective owner