Join 10350+ others. No spamming.
I promise!

Follow us at github.



pinterest / elixometer


A light Elixir wrapper around exometer.



Build Status Coverage Status

A light wrapper around exometer.

Elixometer allows you to define metrics and subscribe them automatically to the default reporter for your environment.


Add the following to your dependencies in mix.exs:

{:elixometer, github: "pinterest/elixometer"}

Then, add :elixometer to your applications. That's it!


In one of your config files, set up an exometer reporter, and then register it to elixometer like this:

       config(:exometer_core, report: [reporters: [{:exometer_report_tty, []}]])
       config(:elixometer, reporter: :exometer_report_tty,
       	    env: Mix.env,
       	    metric_prefix: "myapp")

Metrics are prepended with the metric_prefix, the type of metric and the environment name.

The optional update_frequency key of the :elixometer config controls the interval between reports. By default this is set to 1000 ms in the dev environment and 20 ms in the test environment.

By default, metrics are formatted using Elixometer.Utils.name_to_exometer/2. This function takes care of composing metric names with prefix, environment and the metric type (e.g.

This behaviour can be overridden with a custom formatter function, by adding the following configuration entry:

  config :elixometer, Elixometer.Updater,
    formatter: &MyApp.Metrics.my_custom_formatter/2

Elixometer uses pobox to prevent overload. A maximum size of message buffer, defaulting to 1000, can be configured with:

config :elixometer, Elixometer.Updater,
  max_messages: 5000


Defining metrics in elixometer is substantially easier than in exometer. Instead of defining and then updating a metric, just update it. Also, instead of providing a list of terms, a metric is named with a period separated bitstring. Presently, Elixometer supports timers, histograms, gauges, counters, and spirals.

Timings may also be defined by annotating a function with a @timed annotation. This annotation takes a key argument, which tells elixometer what key to use. You can specify :auto and a key will be generated from the module name and method name.

Updating a metric is similarly easy:

     defmodule ParentModule.MetricsTest do
        use Elixometer

        # Updating a counter
        def counter_test(thingie) do
          update_counter("metrics_test.\#{thingie}.count", 1)

        # Updating a spiral
        def spiral_test(thingie) do
          update_spiral("metrics_test.\#{thingie}.qps", 1)

        # Timing a block of code in a function
        def timer_test do
          timed("metrics_test.timer_test.timings") do

        # Timing a function. The metric name will be [:timed, :function]
        @timed(key: "timed.function") # key will be:
        def function_that_is_timed do

       # Timing a function with an auto generated key
       # The key will be "<prefix>.<env>.timers.parent_module.metrics_test.another_timed_function"
       # If the env is prod, the environment is omitted from the key
        @timed(key: :auto)
        def another_timed_function do

Additional Reporters

By default, Elixometer only requires the exometer_core package. However, some reporters (namely OpenTSDB and Statsd) are only available by installing the full exometer package. If you need the full package, all you need to do is update your mix.exs to include exometer as a dependency and start it as an application. For example:

  def application do
      applications: [:exometer,
      ... other applications go here

  defp deps do
        {:exometer, github: "PSPDFKit-labs/exometer_core"}

In case a reporter allows for extra configuration options on subscribe, you can configure them in your elixometer config like so:

       	    subscribe_options: [{:tag, :value1}])