peoj

peoj

I’m just starting out with Phoenix, thanks for your patience for the basic question that follows:

I want to publish the application start time as a metric.

Here’s what I have so far:

defmodule MyAppWeb.Telemetry do
  use Supervisor
  import Telemetry.Metrics
  
  @application_start_time System.os_time(:second)

  def start_link(arg) do
    Supervisor.start_link(__MODULE__, arg, name: __MODULE__)
  end

  @impl true
  def init(_arg) do
    children = [
      {TelemetryMetricsPrometheus, [metrics: MyAppWeb.Telemetry.metrics()]}
    ]

    
    ## Emit the application start time here
    emit_process_start_time()

    Supervisor.init(children, strategy: :one_for_one)
  end

  def metrics do
    [
      last_value("process.start.time.seconds")
    ]
  end
  
  def emit_process_start_time do
    :telemetry.execute([:process, :start, :time], %{seconds: @application_start_time})
  end
end

When I run the application, the metric is never published. When I manually execute MyAppWeb.Telemetry.emit_process_start_time() from iex, the metric is published.

I think my mistake is that in order for the metric to be exported it must be published after the Telemetry supervision tree has been started, but I’m uncertain of the best way of remedying that. The documentation suggests I should create my own metrics module, but for this simple task that seems a bit overkill. Indeed there may already be a metric that I can reuse that I’m not aware of!

Thanks for reading and for any help!

Showing Posts 1 to 2

hauleth

hauleth

Well, the metric is fired, however it is fired way before the TelemetryMetricsPrometheus started listening to it. What you want to do is to run emit_process_start_time after supervisor children are started. There are few ways to do so:

  1. Fire it in a child:
    children = [
      {TelemetryMetricsPrometheus, [metrics: MyAppWeb.Telemetry.metrics()]},
      {Task, &emit_process_start_time/0}
    ]
    
    Supervisor.init(children, strategy: :one_for_one)
    
  2. Run it after supervisor is started:
    children = [
      {TelemetryMetricsPrometheus, [metrics: MyAppWeb.Telemetry.metrics()]}
    ]
    
    case Supervisor.init(children, strategy: :one_for_one) do
      {:ok, _pid} = ret ->
        emit_process_start_time()
    
        ret
      other -> other
    end
    
  3. Use start_phase/3:
    • add to your application/0 in mix.exs:
      [
        mod: {MyAppWeb.Application, []},
        start_phases: [{:emit, []}]
      ]
      
    • in your application module
      def start_phase(:emit, _type, _args) do
        emit_process_start_time()
      end
      
peoj

peoj OP

Thanks very much! I’ll give those a go.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews