Phillipp
Hey,
I got a list of structs which I need to convert to a map (or similar useful data structure) that I can then further use to create some Prometheus metrics.
Here is what I got. The code is quite dirty in my opinion and maybe there is a smarter way to do it. I wrote it last night at 1am just to get it done, don’t judge me ![]()
Input data:
trackers = [
%{
pause: true,
pause_timeout_in_ms: 72276156,
position: %{"lat" => 11, "lng" => 1},
response: nil,
timeout_in_ms: 309722,
user_id: "5cb6fb2c2071c963d21c517f"
},
%{
pause: false,
pause_timeout_in_ms: false,
position: %{"lat" => 11, "lng" => 1},
response: %{
"status" => "ok",
"vehicle_position" => %{"vehicle" => %{"tracking" => nil}}
},
timeout_in_ms: 1747683,
user_id: "5cb6fb2d2071c963d21c5180"
}
]
Then I do the following:
trackers
|> Enum.map(
fn x ->
state = case x[:pause] do
true -> "paused"
false -> "active"
end
health = case x[:response] do
nil -> "unhealthy"
_ -> "healthy"
end
%{state: state, health: health}
end
)
|> Enum.reduce(
%{
"active" => %{
"healthy" => 0,
"unhealthy" => 0
},
"paused" => %{
"healthy" => 0,
"unhealthy" => 0
}
},
fn (x, acc) ->
put_in(acc[x[:state]][x[:health]], get_in(acc, [x[:state], x[:health]]) + 1)
end
)
(Ignore the inline functions, gonna clean it up after the implementation is set)
Which gives me the following output:
%{
"active" => %{"healthy" => 1, "unhealthy" => 0},
"paused" => %{"healthy" => 0, "unhealthy" => 1}
}
Which I then use the following way:
series = for {state, health} <- extract_labeled_data(trackers), # extract_labeled_data is the cove above
{health, value} <- health do
{[state: state, health: health], value}
end
Prometheus.Model.gauge_metrics(series)
To generate Prometheus metrics like:
app_gateway_tracking_sessions_count{state="active",health="healthy"} 1
app_gateway_tracking_sessions_count{state="active",health="unhealthy"} 0
app_gateway_tracking_sessions_count{state="paused",health="healthy"} 0
app_gateway_tracking_sessions_count{state="paused",health="unhealthy"} 1
I am sure there are some things that can be improved to get from the input data to the final metrics.
Trending in Questions
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
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
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
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
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
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
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
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
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
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex










Showing Posts 1 to 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
mudasobwa
The first step could probably be simplified to:
Now one might
Enum.reduce/3if zeroes are indeed required, otherwiseEnum.map/2would work:Phillipp
I thought about the
group_bybefore but couldn’t wrap my head around it last night.Zeros are indeed required, otherwise the time series are missing. How would the
Enum.reduce/3version look like?mudasobwa
Actually,
Enum.into/3would suffice:Phillipp
That worked wonderfully.
I was even able to simplify my
forcomprehension.mudasobwa
Eh.
Map.to_list/1afterEnum.into/3would do exactly the same.Phillipp
Yeah true. But I will keep the
forin my code so it’s easy to see how the data looks like.mudasobwa
At least you might be slightly more DRY: