{"push_id":1660962459,"size":1,"distinct_size":1,"ref":"refs/heads/patch-1","head":"dd56d46c83ac04e020ce3f0f113034133ddd149e","before":"97c87cf6f1499a624fb43cbb120381c0fe6e6b71","commits":[{"sha":"dd56d46c83ac04e020ce3f0f113034133ddd149e","author":{"name":"David Vassallo","email":"e1d84d47290e0b0092ff0598b21bd6af7d19f5af@gmail.com"},"message":"Fix TimeStamp\n\nThe previous method (using ctime) has a number of issues that make it a bit weird to integrate with popular logging tools like ELK:\r\n\r\n1. It appends a \\n at the end of the timestamp which messes up date formatting for the unwary\r\n2. It outputs time in the local timezone, without actually outputting the timezone... so logging tools like ELK will assume the date is in UTC, when actually it's GMT+2 or whatever... causing silly things like display logs in the future \r\n\r\nEasier method would be as proposed - simply output the timestamp in UNIX/EPOCH format. In this case it's millisecond epoch format - this is far more unambiguous for log parsers","distinct":true,"url":"https://api.github.com/repos/dvas0004/ossec-hids/commits/dd56d46c83ac04e020ce3f0f113034133ddd149e"}]}
{"actor":{"display_login":"dvas0004"}}