{"action":"closed","issue":{"url":"https://api.github.com/repos/mesosphere/marathon-lb/issues/248","repository_url":"https://api.github.com/repos/mesosphere/marathon-lb","labels_url":"https://api.github.com/repos/mesosphere/marathon-lb/issues/248/labels{/name}","comments_url":"https://api.github.com/repos/mesosphere/marathon-lb/issues/248/comments","events_url":"https://api.github.com/repos/mesosphere/marathon-lb/issues/248/events","html_url":"https://github.com/mesosphere/marathon-lb/issues/248","id":163365864,"number":248,"title":"Statsd or collectd metrics?","user":{"login":"ryankennedyio","id":11158006,"avatar_url":"https://avatars.githubusercontent.com/u/11158006?v=3","gravatar_id":"","url":"https://api.github.com/users/ryankennedyio","html_url":"https://github.com/ryankennedyio","followers_url":"https://api.github.com/users/ryankennedyio/followers","following_url":"https://api.github.com/users/ryankennedyio/following{/other_user}","gists_url":"https://api.github.com/users/ryankennedyio/gists{/gist_id}","starred_url":"https://api.github.com/users/ryankennedyio/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ryankennedyio/subscriptions","organizations_url":"https://api.github.com/users/ryankennedyio/orgs","repos_url":"https://api.github.com/users/ryankennedyio/repos","events_url":"https://api.github.com/users/ryankennedyio/events{/privacy}","received_events_url":"https://api.github.com/users/ryankennedyio/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-07-01T10:20:43Z","updated_at":"2016-07-04T03:26:50Z","closed_at":"2016-07-04T03:26:50Z","body":"Hi,\r\n\r\nWe've recently set up a graphite & grafana install for tracking the usual metrics. I'm wondering if there are any suggested best practices for including marathon-lb in our metrics?\r\n\r\nWe handle all response codes in our application layer behind Marathon-lb, but we'd really like to know about the times where marathon returns a 503, or times out because we need more instances running, or similar. Essentially every time a request is sent to us, but isn't handled by our application code, we'd love to know about it.\r\n\r\nWe're using the bobrik/collectd-docker container on each host within our mesos cluster, if that's any help. Sends all data to a graphite database, with Grafana sitting on top."}}
{"actor":{"display_login":"ryankennedyio"}}