{"push_id":1337649647,"size":1,"distinct_size":1,"ref":"refs/heads/feature/aws-metadata-processor","head":"0ca4c1945a985ce8a7570b7b0e1cc708a10e54fc","before":"8e5b4d9ba5943f86fb200d2e61e419391fb62fea","commits":[{"sha":"0ca4c1945a985ce8a7570b7b0e1cc708a10e54fc","author":{"name":"Andrew Kroh","email":"6a1c99f6017c31c13ba8f5a21fb5bfcfa5bd6feb@elastic.co"},"message":"Add EC2, GCE, or DigitalOcean metadata to events\n\nThis introduces a new processor called `cloud_metadata` that detects the hosting provider, caches instance metadata, and enriches each event with the data. There are no configuration options.\n\nSample config:\n\n```\nprocessors:\n- cloud_metadata:\n```","distinct":true,"url":"https://api.github.com/repos/andrewkroh/beats/commits/0ca4c1945a985ce8a7570b7b0e1cc708a10e54fc"}]}
{"actor":{"display_login":"andrewkroh"}}