From: Wladimir <laanwj@gmail•com>
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:46:42 +0200 [thread overview]
Message-ID: <CA+s+GJASND3OU2e+YxUeLmSOW6pTkMwuzHCHeJnnihg6xK9Caw@mail.gmail.com> (raw)
In-Reply-To: <536A8592.8010009@gmail.com>
On Wed, May 7, 2014 at 9:12 PM, Jameson Lopp <jameson.lopp@gmail•com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> In order to gain more insight into what messages and requests a node is processing, I've created a Bitcoin Core fork that outputs statistics to StatsD. I hope that some of you will find this interesting and potentially useful.
>
> http://coinchomp.com/2014/05/07/announcing-statoshi-realtime-bitcoin-node-statistics/
>
> https://jlopp.github.io/statoshi/
>
> Feedback is appreciated!
Ooh nice graphs!
We were coincidentally talking about showing stats from a node on a
local web site on the #bitcoin-dev IRC a few days ago.
At some point, if we're going to offer Bitcoin Core node-only
installers, it'd be nice to include something like this so the user
can keep an eye on their node(s).
Wladimir
next prev parent reply other threads:[~2014-05-07 19:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 19:12 Jameson Lopp
2014-05-07 19:46 ` Wladimir [this message]
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
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+GJASND3OU2e+YxUeLmSOW6pTkMwuzHCHeJnnihg6xK9Caw@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jameson.lopp@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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