| Newsgroups |
gmane.comp.sysutils.pcp |
| Message-ID |
<[email protected]> |
--yabbadabbadoo
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
[speed:master] New Comment on Pull Request #38 Added pcp-mmvstatsd to READM=
E ( https://github.com/performancecopilot/speed/pull/38 )
By fche ( https://github.com/fche ) :
FWIW name toolshedding: "speed-daemon" or calling out this statsd-consumer=
's dependence on golang into its own name seems to focus too much on small =
stuff. The nature & value of the statsd consumer is that it turns statsd pa=
ckets into mmv data, not that it is written in go, nor that it uses the "sp=
eed" golang bindings.
As to one bit about the tool's behaviour: it could make sense for it to re=
tain information about its network peer, for propagation into the mmv outpu=
t namespace. Instead of just ignoring where the packet came from, it could =
pass the address or hostname into the pcp namespace somehow. One way would =
be to prefix the statsd metrics with that info - another way would be to na=
me the mmv "client" files on a per-network-peer basis.
---
[speed:master] New Comment on Pull Request #38 Added pcp-mmvstatsd to READM=
E ( https://github.com/performancecopilot/speed/pull/38 )
By fche ( https://github.com/fche ) :
FWIW name toolshedding: "speed-daemon" or calling out this statsd-consumer=
's dependence on golang into its own name seems to focus too much on small =
stuff. The nature & value of the statsd consumer is that it turns statsd pa=
ckets into mmv data, not that it is written in go, nor that it uses the "sp=
eed" golang bindings.
As to one bit about the tool's behaviour: it could make sense for it to re=
tain information about its network peer, for propagation into the mmv outpu=
t namespace. Instead of just ignoring where the packet came from, it could =
pass the address or hostname into the pcp namespace somehow. One way would =
be to prefix the statsd metrics with that info - another way would be to na=
me the mmv "client" files on a per-network-peer basis.
---
[speed:master] New Comment on Pull Request #38 Added pcp-mmvstatsd to READM=
E ( https://github.com/performancecopilot/speed/pull/38 )
By fche ( https://github.com/fche ) :
FWIW name toolshedding: "speed-daemon" or calling out this statsd-consumer=
's dependence on golang into its own name seems to focus too much on small =
stuff. The nature & value of the statsd consumer is that it turns statsd pa=
ckets into mmv data, not that it is written in go, nor that it uses the "sp=
eed" golang bindings.
@lzap , As to one bit about the tool's behaviour: it could make sense for =
it to retain information about its network peer, for propagation into the m=
mv output namespace. Instead of just ignoring where the packet came from, i=
t could pass the address or hostname into the pcp namespace somehow. One wa=
y would be to prefix the statsd metrics with that info - another way would =
be to name the mmv "client" files on a per-network-peer basis.
--yabbadabbadoo
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
[speed:master] New Comment on Pull Request <a href=3D"https://github.com/p=
erformancecopilot/speed/pull/38">#38 Added pcp-mmvstatsd to README</a><br>
By <a href=3D"https://github.com/fche">fche</a>:<p>
<p>FWIW name toolshedding: "speed-daemon" or calling out this st=
atsd-consumer's dependence on golang into its own name seems to focus too m=
uch on small stuff. The nature & value of the statsd consumer is that =
it turns statsd packets into mmv data, not that it is written in go, nor th=
at it uses the "speed" golang bindings.</p>
<p>As to one bit about the tool's behaviour: it could make sense for it to=
retain information about its network peer, for propagation into the mmv ou=
tput namespace. Instead of just ignoring where the packet came from, it co=
uld pass the address or hostname into the pcp namespace somehow. One way w=
ould be to prefix the statsd metrics with that info - another way would be =
to name the mmv "client" files on a per-network-peer basis.</p>
<p>
<hr><p>
[speed:master] New Comment on Pull Request <a href=3D"https://github.com/p=
erformancecopilot/speed/pull/38">#38 Added pcp-mmvstatsd to README</a><br>
By <a href=3D"https://github.com/fche">fche</a>:<p>
<p>FWIW name toolshedding: "speed-daemon" or calling out this st=
atsd-consumer's dependence on golang into its own name seems to focus too m=
uch on small stuff. The nature & value of the statsd consumer is that =
it turns statsd packets into mmv data, not that it is written in go, nor th=
at it uses the "speed" golang bindings.</p>
<p>As to one bit about the tool's behaviour: it could make sense for it to=
retain information about its network peer, for propagation into the mmv ou=
tput namespace. Instead of just ignoring where the packet came from, it co=
uld pass the address or hostname into the pcp namespace somehow. One way w=
ould be to prefix the statsd metrics with that info - another way would be =
to name the mmv "client" files on a per-network-peer basis.</p>
<p>
<hr><p>
[speed:master] New Comment on Pull Request <a href=3D"https://github.com/p=
erformancecopilot/speed/pull/38">#38 Added pcp-mmvstatsd to README</a><br>
By <a href=3D"https://github.com/fche">fche</a>:<p>
<p>FWIW name toolshedding: "speed-daemon" or calling out this st=
atsd-consumer's dependence on golang into its own name seems to focus too m=
uch on small stuff. The nature & value of the statsd consumer is that =
it turns statsd packets into mmv data, not that it is written in go, nor th=
at it uses the "speed" golang bindings.</p>
<p>@lzap , As to one bit about the tool's behaviour: it could make sense f=
or it to retain information about its network peer, for propagation into th=
e mmv output namespace. Instead of just ignoring where the packet came fro=
m, it could pass the address or hostname into the pcp namespace somehow. O=
ne way would be to prefix the statsd metrics with that info - another way w=
ould be to name the mmv "client" files on a per-network-peer basi=
s.</p>
<p>
<div width=3D"1" style=3D"color:white;clear:both">_._,_._,_</div>
<hr>
Groups.io Links:<p>
You receive all messages sent to this group.
<p>
<a target=3D"_blank" href=3D"https://groups.io/g/pcp/message/15342">View/R=
eply Online (#15342)</a> |
<a target=3D"_blank" href=3D"mailto:[email protected]?subject=3DRe:%20%5Bpcp=
%5D%20Updates%20to%20Github%20%23github%20%23golang">Reply To Group</a>
| <a target=3D"_blank" href=3D"mailto:?subject=3DRe:%20%5Bpcp%5D%20Upd=
ates%20to%20Github%20%23github%20%23golang">Reply To Sender</a>
|
<a target=3D"_blank" href=3D"https://groups.io/mt/4437126?uid=3D174580">=
Mute This Topic</a>
=20
| <a href=3D"https://groups.io/g/pcp/post">New Topic</a><br>
<a href=3D"https://groups.io/mk?hashtag=3Dgolang&subid=3D354243">Mute #gol=
ang</a>
|
<a href=3D"https://groups.io/mk?hashtag=3Dgithub&subid=3D354243">Mute #git=
hub</a>
<p>
<p>pcp mailing list<br />[email protected]<br /><a href=3D"https://groups.io/g=
/pcp/messages" target=3D"_blank">https://groups.io/g/pcp/messages</a></p>
<a href=3D"https://groups.io/g/pcp/editsub?uid=3D174580">Change Your Subsc=
ription</a><br>
<a href=3D"https://groups.io/g/pcp">Group Home</a><br>
<a href=3D"mailto:[email protected]">Contact Group Owner</a><br>
<a href=3D"https://groups.io/static/tos">Terms Of Service</a><br>
<a href=3D"https://groups.io/g/pcp/leave/354243/563757577/xyzzy">Unsubscri=
be From This Group</a><br>
<div width=3D"1" style=3D"color:white;clear:both">_._,_._,_</div>
--yabbadabbadoo--