public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wladimir <laanwj@gmail.com>
To: Jameson Lopp <jameson.lopp@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] statoshi.info is now live
Date: Tue, 13 May 2014 13:43:14 +0200	[thread overview]
Message-ID: <CA+s+GJAoLTrujeHVEUZYDR1mNUFHVsLhH9BYPntrxLKzMm_AEw@mail.gmail.com> (raw)
In-Reply-To: <536FAFEA.5050404@gmail.com>

Hello Jameson,

On Sun, May 11, 2014 at 7:14 PM, Jameson Lopp <jameson.lopp@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Since it seems unlikely that we'll be able to ship an integrated stats / monitoring feature in the short term, I went ahead and set up a public Statoshi instance and threw a nicer interface on top of it.
>
> http://statoshi.info

Must say it looks very nice.

One comment about the graphs: in the 'connected peers' chart you
visualize some larger quantities (especially knownAddresses) and some
very small ones (peer.(dis)connect). This makes the latter invisible
due to scale.

Some random stats may be useful as well:

- Number of connected peers that are SPV clients or full nodes (NODE_NETWORK)
- Current block height (so that it's possible to detect stuck nodes)
- Number of transactions in mempool
- Number of transactions in UTXO set
- Maybe some fee statistics,
https://github.com/bitcoin/bitcoin/pull/3959 would be useful here
- Number of orphan blocks/orphan transactions

Wladimir



  reply	other threads:[~2014-05-13 11:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11 17:14 [Bitcoin-development] statoshi.info is now live Jameson Lopp
2014-05-13 11:43 ` Wladimir [this message]
2014-05-13 17:48   ` Josh Lehan
2014-05-14 11:38     ` Jameson Lopp
2014-05-14 13:10       ` Pieter Wuille

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+GJAoLTrujeHVEUZYDR1mNUFHVsLhH9BYPntrxLKzMm_AEw@mail.gmail.com \
    --to=laanwj@gmail.com \
    --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