{"action":"created","issue":{"url":"https://api.github.com/repos/armon/go-metrics/issues/9","repository_url":"https://api.github.com/repos/armon/go-metrics","labels_url":"https://api.github.com/repos/armon/go-metrics/issues/9/labels{/name}","comments_url":"https://api.github.com/repos/armon/go-metrics/issues/9/comments","events_url":"https://api.github.com/repos/armon/go-metrics/issues/9/events","html_url":"https://github.com/armon/go-metrics/issues/9","id":62822865,"number":9,"title":"Make mapping of metric parts to Prometheus metrics/labels configurable","user":{"login":"juliusv","id":538008,"avatar_url":"https://avatars.githubusercontent.com/u/538008?v=3","gravatar_id":"","url":"https://api.github.com/users/juliusv","html_url":"https://github.com/juliusv","followers_url":"https://api.github.com/users/juliusv/followers","following_url":"https://api.github.com/users/juliusv/following{/other_user}","gists_url":"https://api.github.com/users/juliusv/gists{/gist_id}","starred_url":"https://api.github.com/users/juliusv/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/juliusv/subscriptions","organizations_url":"https://api.github.com/users/juliusv/orgs","repos_url":"https://api.github.com/users/juliusv/repos","events_url":"https://api.github.com/users/juliusv/events{/privacy}","received_events_url":"https://api.github.com/users/juliusv/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2015-03-18T22:54:31Z","updated_at":"2016-08-22T18:09:33Z","closed_at":null,"body":"Prometheus's true power comes from its multi-dimensional data model: metric names with arbitrary key/value dimensions. I wonder if it would be a good idea to allow some configurability of the `PrometheusSink` to allow such mappings. If I understand the go-metrics data model correctly, it's StatsD/Graphite-like, in the sense that a metric simply has a number of parts (separated by dots or whatever else in the end). In Prometheus's statsd-bridge, we already have a very simple mapping language for this type of componentized metric into more useful Prometheus metrics: https://github.com/prometheus/statsd_bridge#metric-mapping-and-configuration\r\n\r\nHowever, it could / should arguably be even a bit more powerful, like allowing regex-based rewriting of metrics and labels.\r\n\r\n/cc @stapelberg, who built the `PrometheusSink` and got bitten by getting the hostname in metric names via this package (via Hashicorp's Raft package using go-metrics)."},"comment":{"url":"https://api.github.com/repos/armon/go-metrics/issues/comments/241499510","html_url":"https://github.com/armon/go-metrics/issues/9#issuecomment-241499510","issue_url":"https://api.github.com/repos/armon/go-metrics/issues/9","id":241499510,"user":{"login":"jeinwag","id":9193234,"avatar_url":"https://avatars.githubusercontent.com/u/9193234?v=3","gravatar_id":"","url":"https://api.github.com/users/jeinwag","html_url":"https://github.com/jeinwag","followers_url":"https://api.github.com/users/jeinwag/followers","following_url":"https://api.github.com/users/jeinwag/following{/other_user}","gists_url":"https://api.github.com/users/jeinwag/gists{/gist_id}","starred_url":"https://api.github.com/users/jeinwag/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeinwag/subscriptions","organizations_url":"https://api.github.com/users/jeinwag/orgs","repos_url":"https://api.github.com/users/jeinwag/repos","events_url":"https://api.github.com/users/jeinwag/events{/privacy}","received_events_url":"https://api.github.com/users/jeinwag/received_events","type":"User","site_admin":false},"created_at":"2016-08-22T18:09:33Z","updated_at":"2016-08-22T18:09:33Z","body":"I did some work on this. Added a PrometheusMapper interface an implemented a basic RegexpMapper, similar to what's possible in jmx_exporter. Please comment."}}
{"actor":{"display_login":"jeinwag"}}