Last modified: 2013-07-31 22:35:23 UTC
Maybe an issue in the deploy scripts? Not sure where/if it was set up before. From the RT ticket I opened: I saw this: http://codeascraft.com/2010/12/08/track-every-release/ and was like "I want that!" Looked in our graphite and found it, kinda: https://graphite.wikimedia.org/render?from=-10days&until=now&width=500&height=380&target=deploy.any In short: we have a Code Deploys metric type (broken down by scap, sync-wikiversion, etc) but it doesn't have any data :(
sync-common-file (among others) have lines like: $BINDIR/deploy2graphite sync-common-file Running it doesn't seem to error obviously at least. reedy@tin:/a/common$ deploy2graphite Usage: /usr/local/bin/deploy2graphite deploytype /usr/local/bin/deploy2graphite will log an entry at graphite.wikimedia.org indicating that a deploy event of the type indicated has occurred. Expected deploy events include sync-common, sync-file, scap, etc. These messages can be suppressed by setting an environment variable . IF YOU'RE RUNNING THIS BY HAND, PLEASE STOP. Go ask Asher why. :) reedy@tin:/a/common$ deploy2graphite test reedy@tin:/a/common$ I see deploys on http://gdash.wikimedia.org/dashboards/reqerror/deploys
Well, odd. I guess I won't use graphite proper.... :)
(In reply to comment #2) > Well, odd. I guess I won't use graphite proper.... :) If you want to use it in graphite proper, you have to apply "display non-zero as infinite" to those metrics. Just like what etsy does, and what I coded into gdash.
(In reply to comment #3) > (In reply to comment #2) > > Well, odd. I guess I won't use graphite proper.... :) > > If you want to use it in graphite proper, you have to apply "display non-zero > as infinite" to those metrics. Just like what etsy does, and what I coded > into > gdash. Ah, thanks, I saw that, but assumed it was enabled on graphite's side somehow for those reports (obviously didn't look too closely)... ok, quiet bug.
