{"push_id":572416126,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"e0a48785f91d5ee9369dc4f0e75093289f005f4a","before":"d85801f76e431c3dab80bd536295f83d03623978","commits":[{"sha":"e0a48785f91d5ee9369dc4f0e75093289f005f4a","author":{"email":"d9233227cd9554f19be23ead79dd5c2fe3ae0988@gmail.com","name":"Robin Humble"},"message":"do not change the timestamp of a node upon receipt of spoofed data\n\ncentrally collected out-of-band data (eg. from BMCs or a blade\nchassis) which is then spoofed into the gmond network does not mean\nthat the node is actually up. unfortunately ganglia's notion of a node\nbeing \"up\" is based upon the time when data was last received by the\ngmond network - the \"REPORTED\" field in gmond's xml. fix this problem\nby not updating the node's timestamp in gmond if the data source is\nspoofed data.\n\nusers that wish to refresh a node's timestamp with spoofed data\n(eg. if a node consists of only spoofed data) can use the -H option\nto gmetric to explicitly send a heartbeat message and keep the node\nin the \"up\" state.","distinct":true,"url":"https://api.github.com/repos/plaguedbypenguins/monitor-core/commits/e0a48785f91d5ee9369dc4f0e75093289f005f4a"}]}