From: Mike Hearn <mike@plan99.net>
To: Jameson Lopp <jameson.lopp@gmail.com>
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Announcing the Statoshi fork
Date: Wed, 7 May 2014 21:50:53 +0200 [thread overview]
Message-ID: <CANEZrP1A0z0sVBHzW_2Z1RJ6STX9G1RW_KncbY_yN7NuTL8BZw@mail.gmail.com> (raw)
In-Reply-To: <536A8592.8010009@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
Really nice! We definitely need to put together a team who really cares
about the operations side of the network and this is a fantastic start.
It'd be nice if you didn't assume knowledge of what statsd is out of the
box. Given the name I'd assumed it was a small UNIX daemon but it seems
it's actually a Javascript thingy?
It looks like putting together a monitored bitcoind setup can be quite a
lot of work. I wonder if there are ways to simplify it. For example, would
it make sense for someone to run a community statsd and graphite instance,
so we can get aggregate statistics across many nodes and the node operators
don't have to set everything up themselves? Does that make any sense?
[-- Attachment #2: Type: text/html, Size: 804 bytes --]
next prev parent reply other threads:[~2014-05-07 19:51 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
2014-05-07 20:35 ` Jameson Lopp
2014-05-07 21:04 ` Charlie 'Charles' Shrem
2014-05-07 19:50 ` Mike Hearn [this message]
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=CANEZrP1A0z0sVBHzW_2Z1RJ6STX9G1RW_KncbY_yN7NuTL8BZw@mail.gmail.com \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jameson.lopp@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