{"action":"opened","issue":{"number":21,"created_at":"2011-10-27T01:45:15Z","pull_request":{"diff_url":null,"patch_url":null,"html_url":null},"body":"Need a way to assert that e.g. database servers should display additional metric paths over the 'baseline' metric group, such as postgres lag or whatnot.\r\n\r\nThis is partially served by having \"wide ranging\" metrics in the baseline (such as `df`) and then using the `exclude` feature to trim things down; thus a DB server will already display its DB partition information.\r\n\r\nSo we could solve this by padding out `baseline` with all possibly useful metrics and just ensure that if a host lacks a metric, we don't try to show it.\r\n\r\nOtherwise, we need a way to associate hosts with optional extra metrics, meaning another config chunk that maps hostnames to metric lists. Not hard, if config-generated; anything hand-oriented might need to allow keying off hostname/globbing/etc.","comments":0,"title":"Role/non-basic metrics","updated_at":"2011-10-27T01:45:15Z","url":"https://api.github.com/repos/bitprophet/fullerene/issues/21","id":2063817,"assignee":null,"milestone":null,"closed_at":null,"user":{"gravatar_id":"f1acc6318028fdba9874c77bc622a2fb","avatar_url":"https://secure.gravatar.com/avatar/f1acc6318028fdba9874c77bc622a2fb?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","url":"https://api.github.com/users/bitprophet","id":6088,"login":"bitprophet"},"html_url":"https://github.com/bitprophet/fullerene/issues/21","labels":[],"state":"open"},"legacy":{"number":21,"action":"opened","issue":2063817}}