Re: Implementing a monitoring system with django.

Depending on what you need for the graphs,have a look at flot,jqplot or rapheal.js(heavy).There is also high charts althought there are some licensing issues you may want to avoid.

If you get stuck with the charts,let me know..am running some.

On Tuesday, December 11, 2012 11:09:06 PM UTC+2, Marc Aymerich wrote:

On Tue, Dec 11, 2012 at 4:32 PM, Bill Freeman <ke1...@gmail.com> wrote:
>
>
> On Mon, Dec 10, 2012 at 2:41 PM, Marc Aymerich <glic...@gmail.com> wrote:
>>
>> Hi,
>> I'm considering to implement a simple monitorization system that
>> basically gathers some data from a set of nodes (<1000 nodes). The
>> gathered data should be stored in order to let users perform some
>> queries and maybe also generate some graphs.
>>
>> I'm looking for advice in what components are best suited for each of
>> the following parts:
>>
>> 1) Storage: maybe something nonsql like MongoDB? or perhaps RRD?
>> 2) Data gathering: celery periodic tasks?
>> 3) Graphs: rrd? or some java script framework for graphing?
>>
>> thanks for your comments!!
>
>
> While this may be a fine opportunity to learn about some of these techniques
> (NoSQL, celery), unless I misunderstand the potential bandwidths involved,
> the problem fits more pedestrian stuff pretty well.
>
> If I were doing this I'd use PostgreSQL and a cron (or equivalent on your
> OS) triggered django management command to gather the data and stuff it into
> the models.  Certainly django can provide display of the data to the user.
>
> For graphing, I've used YUI (yahoo) tools in the past (I'm sure that google
> has competitive offerings), but it required that the user have Flash.  While
> pretty much everyone has Flash, I'd rather go for HTML5 or SVG (and a few
> people may have browsers that don't do these).  Maybe modern frameworks can
> be had that detect the browser's capabilities and respond accordingly.  (The
> YUI stuff was driven by a table of data in the DOM, and that approach allows
> the support decision to be deferred to the browser side.)  Depending on load
> and update rate, you could also generate png or jpg files on the fly in a
> view that IMG tags in your HTML refer to, which works even if the user has
> javascript disabled, but loads the server a bit.  You would probably want to
> encode a timestamp or generation sequence into the generated image path
> name, so that you wouldn't have to worry about cacheing, including in the
> browser, keeping you from showing a fresh image when the user refreshes the
> page.
>

Hi bill thanks for your feedback!
You're right, maybe I can start using a traditional RDBMS like
postgres and switch when things starts getting slow, if even it really
happens at all.

By the way, I've been looked at some nosql storage backends, and
couchdb seems the more appropriate option for storing time-series data
in django.

regarding the graph stuff, the project is somehow related with
opensource and openeverything, so flash is not really an option. I'll
look at some js framework.

thanks again!
--
Marc

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/pxDyxFeEwBoJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.