justinaiken / adhearsion-stats

Stats sending for Adhearsion

💎

Find me at:

• justinaiken.com
• Framebridge

Liberal AF: #BLM #LGBTQ 🇺🇦

🖕 Fuck Trump, Fuck Putin 🖕

adhearsion-stats's Issues

Namespace probes

I'm not sure if this belongs in the library hard-coded, should be config, or should be left up to the Application exclusively. But I did something like this to namespace my probes to make it easier to separate development from production. This module was mixed in so that every call go #gauge, #increment or #timing had prefixes:

module CoreUtility
  def gauge(*args)
    AdhearsionStats.gauge prefixed_label(args.shift), *args
  end

  def increment(*args)
    # Increment gets a special label so it shows up in Graphite at a similar
    # nesting level to timers and gauges
    AdhearsionStats.increment "counters.#{prefixed_label(args.shift)}", *args
  end

  def timing(*args)
    label = prefixed_label args.shift
    if block_given?
      start = Time.now
      yield
      value = Time.now - start
    else
      value = args.shift
    end
    AdhearsionStats.timing label, value
  end

  def prefixed_label(label)
    "#{Adhearsion.config.platform.environment}.#{node_name}.#{label}"
  end

  def node_name
    @node_name ||= Socket.gethostname.split('.').first
  end
end

Should hook into Adhearsion's exception catcher

We should create a default counter for each exception that is raised within an Adhearsion app

Should hook into Adhearsion's Statistics class

Would be cool if there was an option to hook into Adhearsion::Statistics with this plugin, so that graphite could graph all those stats with no programming needed on the users part...

• Perhaps monkey-patch these 4 methods
• Or maybe alias Celluloid::Actor[:statistics] to Celluloid::Actor[:statistics_original] and insert our own Celluloid::Actor[:statistics] that also sends stats.
• Or maybe leave the built in stats alone, and just register our own event handlers in a similar fashion..