[erlang-questions] problems getting bigwig deps

[Tim Watson]

I started a project up before bigwig appeared, which was based on the
multi-node monitoring premise. https://github.com/hyperthunk/nodewatch - it
is very similar in terms of the monitoring design, except that it delegates
to the excellent eper library to do the work of shuffling code onto nodes
and subscribing to monitoring events. The web side of it was a complete
hack for a demo however, and bigwig is much better put together in that
respect. Perhaps we could share some ideas, as I'd be glad to contribute if
there's an opportunity to do so and I think the whole community will
benefit from a good distributed monitoring capability like this.

Cheers,

Tim

On 1 November 2011 14:39, Loïc Hoguin <essen@REDACTED> wrote:

> On 11/01/2011 02:06 PM, Paul Oliver wrote:
> > On Tue, Nov 1, 2011 at 12:56 PM, Tim Watson <watson.timothy@REDACTED>
> wrote:
> >> On 1 November 2011 12:52, Paul Oliver <puzza007@REDACTED> wrote:
> >>>
> >>> I've updated Bigwig to use extend's version of cowboy.
> >>>
> >>> https://github.com/beamspirit/bigwig
> >>>
> >>> Cheers,
> >>> Paul.
> >>
> >> Are you likely to continue adding features to bigwig, or is it on hold
> for
> >> the time being?
> >
> > I'm definitely keen to progress it.  I'd like to add multi node
> > support.  Do you have any suggestions?
>
> At the very least separate the probing of data from the display side
> into two (or more) applications. That way we can just deploy probes on
> nodes we want to monitor and have a separate node with just the server
> application running. Also would save the trouble for people needing a
> specific version of cowboy different than yours on their server.
>
> I'd personally go for many small probes with a common interface for data
> retrieval, that way you can choose the probes to include, maybe write
> your own independently from the bigwig project, etc.
>
> We should speak together before the 15th as I'll need to work on that by
> then. :)
>
> --
> Loďc Hoguin
> Dev:Extend
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20111101/ac8083a2/attachment.htm>