Migrating from graphite to graph-explorer

痴心易碎 提交于 2020-01-05 02:49:23

问题


The graphite-webapp does not encourage ad-hoc graphing. Graphiti et al are just fancy UIs that, while improve UI-UX, do not do much regarding the inherent linear metric search that plagues the graphite-webapp. Correct me if wrong here, but the only option I came across that encourages ad-hoc graphing has been Graph-Explorer. Assuming, that Graph-Explorer is the only way ahead.

I have some 1000 distinct metrics currently. Named in the following fashion-

stats.beta.pluto.ip-10-0-1-81.helios.pa.v4.reminder.total

stats.beta.pluto.ip-10-0-1-81.helios.pa.v4.reminder.failed

stats.beta.pluto.ip-10-0-1-81.helios.pa.v4.reminder.delivered

stats.dev.ganglia.ip-10-0-3-40.ink.web.pi.notification.android.total stats.dev.ganglia.ip-10-0-3-40.ink.web.pi.notification.android.failed stats.dev.ganglia.ip-10-0-3-40.ink.web.pi.notification.android.delivered

I understand that these will become-

metric=stats.env=dev.role=ganglia.server=ip-10-0-3-40. application=ink.endpoint=web.src=pi.metric=notification.what=total

Where do I insert unit and target_type tags?

Similarly, I have 500 timers.

  1. How do I go about migrating from 'proto1' to 'proto2'?

  2. Also where exactly does Carbon-Tagger come into the stack?

  3. Do I rename my metrics at the source level?

  4. Do I modify the structured_metrics/plugins/statsd.py file as we have fixed hierarchy across our distributed infrastructure?

  5. Anything I am missing?

  6. What will I have to change in my statsd? I quote the carbon-tagger documentation- "aggregators like statsd will need proto2 support."


回答1:


the structured metrics plugins will set the tags for proto1 ("old style") metrics, see https://github.com/vimeo/graph-explorer/wiki/Structured-Metrics

if you want to stick to proto1 you just have to create a plugin to tag your metrics see https://github.com/vimeo/graph-explorer/wiki/Structured-Metrics#writing-your-own-plugins and existing plugins for examples

you can basically ignore carbon-tagger if you want to stick with proto1, so 3 is not needed, but otherwise yes. the statsd plugin just converts statsd's internal metrics to proto2.



来源:https://stackoverflow.com/questions/18651477/migrating-from-graphite-to-graph-explorer

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!