public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wladimir <laanwj@gmail.com>
To: Nelson Castillo <nelsoneci@gmail.com>
Cc: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Announcing the Statoshi fork
Date: Thu, 8 May 2014 13:22:46 +0200	[thread overview]
Message-ID: <CA+s+GJA6DzzoX4tod2FSV_L02Ne4exuNh_e9fOQfWFmCAMTKUQ@mail.gmail.com> (raw)
In-Reply-To: <CAPFxkVmPVp01hVMbNsseOJ=5MyCCQ9J1cYChK3-Z93UDp6qP9Q@mail.gmail.com>

On Wed, May 7, 2014 at 10:28 PM, Nelson Castillo
> Is SNMP an option? That way you do not need to implement clients and there
> are many tools written.

It's always good to use an existing standard, but I remember SNMP,
even on a client device/application is pretty complex in itself.

And I suppose the registration for custom OIDs and such is kind of baroque.

I'm not entirely convinced of what the added value in this case would
be. Yes, there are tools for monitoring SNMP, but in my experience
those tools usually support other ways of collecting statistics as
well.

Wladimir



  reply	other threads:[~2014-05-08 11:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 19:12 [Bitcoin-development] Announcing the Statoshi fork Jameson Lopp
2014-05-07 19:46 ` Wladimir
2014-05-07 19:57   ` Jameson Lopp
2014-05-07 20:18     ` Wladimir
2014-05-07 20:25       ` Mike Hearn
2014-05-07 20:31         ` Charlie 'Charles' Shrem
2014-05-07 21:07         ` Wladimir
2014-05-08  0:47           ` Gregory Maxwell
2014-05-08  7:45             ` Wladimir
2014-05-08 10:08               ` Mike Hearn
2014-05-08 10:32                 ` Wladimir
2014-05-07 20:28       ` Nelson Castillo
2014-05-08 11:22         ` Wladimir [this message]
2014-05-07 20:35       ` Jameson Lopp
2014-05-07 21:04         ` Charlie 'Charles' Shrem
2014-05-07 19:50 ` Mike Hearn
2014-05-07 20:00   ` Jameson Lopp
2014-05-07 20:12     ` Mike Hearn
2014-05-07 19:55 ` Pavol Rusnak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+s+GJA6DzzoX4tod2FSV_L02Ne4exuNh_e9fOQfWFmCAMTKUQ@mail.gmail.com \
    --to=laanwj@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=nelsoneci@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox