{"action":"opened","issue":{"url":"https://api.github.com/repos/mailgun/godebug/issues/21","labels_url":"https://api.github.com/repos/mailgun/godebug/issues/21/labels{/name}","comments_url":"https://api.github.com/repos/mailgun/godebug/issues/21/comments","events_url":"https://api.github.com/repos/mailgun/godebug/issues/21/events","html_url":"https://github.com/mailgun/godebug/issues/21","id":72541880,"number":21,"title":"Useful for metrics","user":{"login":"joeblew99","id":11999859,"avatar_url":"https://avatars.githubusercontent.com/u/11999859?v=3","gravatar_id":"","url":"https://api.github.com/users/joeblew99","html_url":"https://github.com/joeblew99","followers_url":"https://api.github.com/users/joeblew99/followers","following_url":"https://api.github.com/users/joeblew99/following{/other_user}","gists_url":"https://api.github.com/users/joeblew99/gists{/gist_id}","starred_url":"https://api.github.com/users/joeblew99/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joeblew99/subscriptions","organizations_url":"https://api.github.com/users/joeblew99/orgs","repos_url":"https://api.github.com/users/joeblew99/repos","events_url":"https://api.github.com/users/joeblew99/events{/privacy}","received_events_url":"https://api.github.com/users/joeblew99/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-05-01T22:49:08Z","updated_at":"2015-05-01T22:49:08Z","closed_at":null,"body":"This is very simple, but I like it.\r\nI think metrics can also be done this way. On large deployment foot print projects fixing a bug can require putting in a metric to watch it in production.\r\n\r\nI also like the idea of putting in alarms and weightings in the code.\r\n\r\nThe devops team can't know what to measure at the application level. They only know high level generic things they need to measure.\r\n\r\nWhat do people think of develops being able to describe these aspects in the code at design time ??"}}