From: "Scott H." <lists@...>
Date: 2012-03-26T12:15:03+09:00
Subject: Re: Undecided on how to approach a problem of storing html tables in a database

Allan Wind wrote in post #1053267:
>
> You can store arbitrary data in text fields, but you lose many of
> benefits (schema, searching, indexing, joins etc).  There are
> mysql plugins, I believe, to deal with json in the database.
> There are other serialization formats you could consider (say,
> protobuf).
>
> Have you looked into any of the NoSQL databases yet?  Redis might
> be a better fit for key-value, or you could go the document
> database route with CouchDB or MongoDB.
>
Hi Allan,
I've not looked at anything other than MySQL right now - good idea, I'd 
not considered any of the other plugins or NoSQL DBs - that might be 
interesting
>
> Can you store the data in mysql, templates elsewhere and render
> the combination either on demand or periodically?
>
> Any particular reason why you building this from scratch?  There
> are a ton of systems out there already (nagios, munin, cacti,
> etc).  Most of these make it fairly easy to write custom plugins.
> serverfault might be a good place to cruise for ideas.
>
I suppose the main thing I'm really looking at is how to solve a 
particular business problem that we've got - ideally we'd ship a simple 
product that we can use to generate historical data on our products - 
the end goal will be to have the product collect transient logs when 
certain events occur - but these tend to be non-trappable so SNMP is out 
for approx 60% of what we want to do
Munin and Cacti look really interesting, so it's worth me spending a bit 
of time looking to see what I can collect and store.

-- 
Posted via http://www.ruby-forum.com/.