[erlang-questions] app for watching/monitoring other erlang nodes

Vlad Dumitrescu vladdu55@REDACTED
Thu Dec 13 10:56:17 CET 2012

Thanks Jesper,

It was the configuration part that I feel is something that I don't want to
learn unless it's absolutely necessary. For a one-time simple job, there
are better alternatives, I think.

In my case, it was pointed out to me that erlang:system_monitor/2 can make
the runtime send messages when a process gets too large, which is 98% of
what I needed to do.


On Thu, Dec 13, 2012 at 10:50 AM, Jesper Louis Andersen <
jesper.louis.andersen@REDACTED> wrote:

> On Nov 20, 2012, at 1:46 PM, Vlad Dumitrescu <vladdu55@REDACTED> wrote:
> > Yes, you're right, snmp matches the description, but it feels a bit too
> heavy for me. I will read about it, maybe it's not true. I would like to
> have the monitored nodes without any specific application running, just
> answering to some RPCs once in a while.
> The SNMP agent parts are not that hard to use. Basically you define a MIB
> file which exposes the values your system supports. Then you define a
> mapping from the MIB file to Erlang functions, or to a mnesia table. The
> SNMP subsystem then responds on requests and calls the appropriate Erlang
> code, wraps things in ASN.1 and so on.
> What makes it "heavy" is that SNMP itself is rather heavy. And that there
> is quite some configuration needed in order to expose these values to the
> rest of the world. The advantage is, however, that once you have set it up
> properly, it is extremely easy to add more metrics and probes to your node.
> Erlang/OTP also provides a couple of  things itself for monitoring.
> Including "what process uses the most memory and how much" etc.
> Jesper Louis Andersen
>   Erlang Solutions Ltd., Copenhagen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20121213/e95b65a0/attachment.htm>

More information about the erlang-questions mailing list