从石墨迁移到图形浏览器 [英] Migrating from graphite to graph-explorer

查看:138
本文介绍了从石墨迁移到图形浏览器的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

石墨Web应用程序不鼓励临时图形化. Graphiti等人只是幻想中的UI,尽管改进了UI-UX,但在困扰石墨Web应用程序的固有线性度量搜索方面做得并不多.如果在这里出错,请纠正我,但是我遇到的鼓励临时图形化的 only 选项是图形浏览器.假设,Graph-Explorer是前进的唯一途径.

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.

我目前有大约1000个不同的指标.以以下方式命名-

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

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

我知道这些会变成-

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

我在哪里插入unittarget_type标签?

类似地,我有500个计时器.

Similarly, I have 500 timers.

  1. 如何从"proto1"迁移到"proto2"?

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

Carbon-Tagger 到底在哪里?

我是否在源级别重命名指标?

Do I rename my metrics at the source level?

由于在分布式基础结构中具有固定的层次结构,我是否修改structured_metrics/plugins/statsd.py文件?

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

我想念什么吗?

我的statsd需要更改什么?我引用了carbon-tagger文档-像statsd这样的聚合器将需要proto2支持."

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

推荐答案

结构化指标插件将设置proto1(旧样式")指标的标签,请参见

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

如果您想坚持使用proto1,只需创建一个插件来标记指标即可,请参见

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

如果要坚持使用proto1,则基本上可以忽略碳纤维标尺,因此不需要3,否则可以. statsd插件只是将statsd的内部指标转换为proto2.

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.

这篇关于从石墨迁移到图形浏览器的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆