From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WjXKW-0004nF-6c for bitcoin-development@lists.sourceforge.net; Sun, 11 May 2014 17:14:28 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.49 as permitted sender) client-ip=209.85.216.49; envelope-from=jameson.lopp@gmail.com; helo=mail-qa0-f49.google.com; Received: from mail-qa0-f49.google.com ([209.85.216.49]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WjXKV-0007k2-AD for bitcoin-development@lists.sourceforge.net; Sun, 11 May 2014 17:14:28 +0000 Received: by mail-qa0-f49.google.com with SMTP id cm18so6069609qab.36 for ; Sun, 11 May 2014 10:14:21 -0700 (PDT) X-Received: by 10.140.32.195 with SMTP id h61mr20201199qgh.10.1399828461696; Sun, 11 May 2014 10:14:21 -0700 (PDT) Received: from ?IPv6:2606:a000:b042:c601:13f:7b1e:daeb:4d3c? ([2606:a000:b042:c601:13f:7b1e:daeb:4d3c]) by mx.google.com with ESMTPSA id f106sm8257923qge.8.2014.05.11.10.14.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 11 May 2014 10:14:20 -0700 (PDT) Message-ID: <536FAFEA.5050404@gmail.com> Date: Sun, 11 May 2014 13:14:18 -0400 From: Jameson Lopp User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Bitcoin Dev X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (jameson.lopp[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WjXKV-0007k2-AD Subject: [Bitcoin-development] statoshi.info is now live X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2014 17:14:28 -0000 -----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 You can also view the raw Graphite stats at http://statoshi.info:8080/ If there are any metrics that you think would be helpful for development or monitoring purposes, just let me know and I'll take a shot at adding them. Jameson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJTb6/qAAoJEIch3FSFNiDceR4H/jHchii5offrnQRsRcA7o4bh EEeL7ln9ID2FtqpL5wEjFtYq7nXL/8+o1BY7MOULo4SMpQIi0aY3ehNkPUCX3XKh U0F1ZZpkjMpI8BbIqBFwspNAE7bFh8vmRW9/IhWXf3VY8TmgVhZnbMmzxvcw7DwI kb1pgXZOEKCwmMvxBoWdmwDogvZvNPIThoQ9InY+qaGQut3lvrrSQMR7jYXxTY/9 Rebnny5c15KUrM3xwRPJvFHlbFE8F5a6ue9uwGq/STK73/iDqXksJNFnpzk3fnGc AryWmleHFfttfsb1kb991BFn2RCaKWvGBNUnq5dD/cCZIBwu3F16j65JAxboF94= =Xe+e -----END PGP SIGNATURE-----