graphite

I have an application that publishes a number of stats to graphite via statsd. One of the stats simply sends a stat increment to statsd every time a message is received by the service. I need to display a graph that shows the the relative traffic over time for this stat. Generally speaking, I should be able to display a graph that refreshes every, say 10 seconds, and displays how many messages were recived in those 10 seconds as well as the history for a given period of time. However, no matter how I format my API query I cannot seem to get accurate data. I've read a number of articles

http://www.cnblogs.com/txwsqk/p/6522854.html # Function plugins FUNCTION_PLUGINS = ['linkedme.aliasByMap',] /opt/graphite/webapp/graphite/functions/custom# ls __init__.py __init__.pyc linkedme.py linkedme.pyc #coding:utf-8 from graphite.functions.params import Param, ParamTypes def aliasByMap(requestContext, seriesList): kv = { '4000054':'你想展示的内容', } for series in seriesList: series.name = kv[series.name] return seriesList aliasByMap.group = 'Alias' aliasByMap.params = [ Param('seriesList', ParamTypes.seriesList, required=True), ] SeriesFunctions = { 'aliasByMap': aliasByMap, } 这样 grafana

We have etsy/statsd node application running that flushes stats to carbon/whisper every 10 seconds. If you send 100 increments (counts), in the first 10 seconds, graphite displays them properly, like: localhost:3000/render?from=-20min&target=stats_counts.test.count&format=json [{"target": "stats_counts.test.count", "datapoints": [ [0.0, 1372951380], [0.0, 1372951440], ... [0.0, 1372952460], [100.0, 1372952520]]}] However, 10 seconds later, and this number falls to 0, null and or 33.3. Eventually it settles at a value 1/6th of the initial number of increments, in this case 16.6 . /opt/graphite

I have been exploring the Graphite graphing tool for showing metrics from multiple servers, and it seems that the 'recommended' way is to send all metrics data to StatsD first. StatsD aggregates the data and sends it to graphite (or rather, Carbon). In my case, I want to do simple aggregations like sum and average on metrics across servers and plot that in graphite. Graphite comes with a Carbon aggregator which can do this. StatsD does not even provide aggregation of the kind I am talking about. My question is - should I use statsd at all for my use case? Anything I am missing here? StatsD

关键词： 监控 、dashboard、PHP、graphite、statsd、whisper、carbon、grafana、influxdb、Python 本文档适用人员：研发和运维员工 提纲： 监控平台要做到什么程度？为什么要自己做？ 几个通用技术问题 绘图所依赖的数据如何收集？如何加工？如何存储？ 图形如何绘制，各种指标如何叠加？ 拓扑关系如何绘制？ 技术选型哲学 最终选了statsd+graphite 数据的采集 数据存储的粒度 天机的技术选型 一，监控平台要做到什么程度？为什么要自己做？ 运维监控满满都是着各种开源系统以及它们的 Dashboard： Zabbix Nagios Centreon Logstash Ganglia+Cacti 以及各种业务指标趋势的 Dashboard。 我们认为，监控不能只是各种数据的采集和罗列，不仅仅是弄若干个报表并进一步配置成仪表盘， 而是有一定智能，仿照我们日常的排查问题思路，建立一定规则，自动检查，深度检查，友情提示 。 随手举一个例子： 规则：模仿我们发现问题后先检查数据库主从同步是否有问题的习惯 天机系统发现成单金额或验证券数或短信发送条数环比大幅下降后，启动检查规则， 自动逐一检查各种从库的主从同步情况。 如果发现主从延迟超过阈值，则天机 DashBoard 应浮出两条红色警告提示（可点击进入）： 5分钟销售数据环比下降50%

I'm trying to divide 2 series to get their ratio. For example I'm got sites (a.com, b.com, c.com) as * (All sites) Each of them has total sections count and errors occurred stats. I'm wanna to show as bars errors/sections where section > errors for each site to each erros for this site. Here I'm whant to got 3 bars. So: A parser.*.sections.total B parser.*.errors.total X-Axis Mode:Series Display:DrawMode: Bars When i'm trying to use divideSeries I'm always got VallueError (divideSeries second argument must reference exactly 1 series) You can use mapSeries with divideSeries to do vector

require 'statsd' statsd = Statsd.new('localhost', 8125).tap{|sd| sd.namespace = 'account'} 1.times do statsd.increment 'hitcount4' end sleep 5 5.times do statsd.increment 'hitcount4' end sleep 10 10.times do statsd.increment 'hitcount4' end i am using ruby gem statsd-ruby i ran the above script it executes successfully, and the graph appears but i can just see the a line over the x-axis and nothing (no value for y-axis), how to get the graph for above script? i want to record each increment call. contents of /opt/graphite/statsd/local.js { graphitePort: 2003 , graphiteHost: "127.0.0.1" , port: