📅 Original date posted:2014-05-07
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I completely agree that this setup is far too difficult to reasonably expect anyone to implement it. You're correct that we could run a single StatsD daemon and have quite a few nodes sending statistics to it - this is really what StatsD was designed for - sampling small amounts of stats from high volume systems. There would be an issue of trust, however - StatsD was also only really designed to be run inside of highly secure infrastructure where you trust all of the machines that are talking to it.
- - Jameson
On 05/07/2014 03:50 PM, Mike Hearn wrote:
> 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?
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTapDsAAoJEIch3FSFNiDcqNMIAKbliLXVJ+CovCB+etqwCYfD
oTs0uxEIZvnGSzqn6i3z4tgzF7kbnpVThiHpG2MO2BytasGzfr+FsDLFpvkkvx0Q
yffa1J5uB5QhY/POwg6GCN4DEmy8tbd+I5rSTKg1m/JuXZV2B4TFgr6GF+t+gBNT
O2TTIngcl77XbGDF2XKOZSAHaIFx2KjdZNg5lfInVxDeA1dDzlU/vmEB37fx80EH
IzD7FTllLp5qhlwYxaQTVxXmbjy+pXbtArYsVSRgoscgJI3DDKpxQj3uzjxouEHv
27QkhuS2dzFioQhLPcnz/PtcCkE1l0aDNf6n7OiJ3lGygQ0+AKZHpyuvFujpSY8=
=QCYI
-----END PGP SIGNATURE-----
Jameson Lopp [ARCHIVE] /
npub1gh…akqmn
2023-06-07 15:21:08
in reply to nevent1q…g2dz
Author Public Key
npub1ghgfr3aumwuxwnwghywxpaejxpf6k9pjcnyg9lfdnztlu5pwa0ksyakqmnPublished at
2023-06-07 15:21:08Event JSON
{
"id": "d9b0b90deaf174e294c7bacf99c647946b05c905345555ca5dc69ad20b2e8c94",
"pubkey": "45d091c7bcdbb8674dc8b91c60f7323053ab1432c4c882fd2d9897fe502eebed",
"created_at": 1686151268,
"kind": 1,
"tags": [
[
"e",
"eee9f45331490750cb4b2457486fbbd67822220193953d499fd36e4811e321a2",
"",
"root"
],
[
"e",
"6f795e504885681b59045aca116d12d0cf551c04af5b0d658ad9c496063c07fb",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2014-05-07\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\nI completely agree that this setup is far too difficult to reasonably expect anyone to implement it. You're correct that we could run a single StatsD daemon and have quite a few nodes sending statistics to it - this is really what StatsD was designed for - sampling small amounts of stats from high volume systems. There would be an issue of trust, however - StatsD was also only really designed to be run inside of highly secure infrastructure where you trust all of the machines that are talking to it.\n\n- - Jameson\n\nOn 05/07/2014 03:50 PM, Mike Hearn wrote:\n\u003e Really nice! We definitely need to put together a team who really cares\n\u003e about the operations side of the network and this is a fantastic start.\n\u003e \n\u003e It'd be nice if you didn't assume knowledge of what statsd is out of the\n\u003e box. Given the name I'd assumed it was a small UNIX daemon but it seems\n\u003e it's actually a Javascript thingy?\n\u003e \n\u003e It looks like putting together a monitored bitcoind setup can be quite a\n\u003e lot of work. I wonder if there are ways to simplify it. For example, would\n\u003e it make sense for someone to run a community statsd and graphite instance,\n\u003e so we can get aggregate statistics across many nodes and the node operators\n\u003e don't have to set everything up themselves? Does that make any sense?\n\u003e \n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.14 (GNU/Linux)\nComment: Using GnuPG with Thunderbird - http://www.enigmail.net/\n\niQEcBAEBAgAGBQJTapDsAAoJEIch3FSFNiDcqNMIAKbliLXVJ+CovCB+etqwCYfD\noTs0uxEIZvnGSzqn6i3z4tgzF7kbnpVThiHpG2MO2BytasGzfr+FsDLFpvkkvx0Q\nyffa1J5uB5QhY/POwg6GCN4DEmy8tbd+I5rSTKg1m/JuXZV2B4TFgr6GF+t+gBNT\nO2TTIngcl77XbGDF2XKOZSAHaIFx2KjdZNg5lfInVxDeA1dDzlU/vmEB37fx80EH\nIzD7FTllLp5qhlwYxaQTVxXmbjy+pXbtArYsVSRgoscgJI3DDKpxQj3uzjxouEHv\n27QkhuS2dzFioQhLPcnz/PtcCkE1l0aDNf6n7OiJ3lGygQ0+AKZHpyuvFujpSY8=\n=QCYI\n-----END PGP SIGNATURE-----",
"sig": "34c8f5a63fb7a5b6c795a4a8615ba1e0ee4ffe164b41fdba44683f54e61a5010b6d0ff88f43561d1811cdb92ea54048f77c49f3bd705447fc1b20587d6dc8323"
}