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
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
Hey guys,
I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly
Do you guys have any suggestions what is the best prac...
New
Kia ora,
We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I have what I’ve heard referred to as a “lookup table” in my database. This is a way of assigning codes to common values. One common lo...
New
Hello,
I’m developing a online persistent chat system (what’s app) like using elixir/dynamodb/aws for a mobile app(flutter).
The diffic...
New
What approach to take when sending live updates to “random” users Hi! I have a question, I have a little chat app, and when I create a DM...
New
Other Trending Topics
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
There are three potential reasons for members of this forum to have a look at https://vutuv.de
You are tired or annoyed of LinkedIn.
Yo...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #iex
- #elixirconf-us
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming











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: