TLDR; I added labels to the process nodes to make it more clear what the processes represent.
I was using Kino.Process in Livebook to try and figure out how some elements of the Membrane RTC Engine work. I won't go into the details, but suffice to say this is a foreign code base to me, and it wasn't clear from the get go:
What the supervision tree looks like.
How it the internal genservers relate to each other.
How that ties into my phoenix app.
So I was poking around blindly until I got my RTC Engine's process's graphed with Kino. This is what it looked like for reference:
Cool! So now I get to see the process layout, but I'm still blind as to what all this actually is. I still don't know what Membrane is doing. To get a bit more insight, changed the label for the PID node to also print out the node's id and got this:
This helped me relate my WebRTC endpoints with pid's and I also really like the insight it gives when you plot a Phoenix app's supervision tree.
Hi there!
TLDR; I added labels to the process nodes to make it more clear what the processes represent.
I was using
Kino.Process
in Livebook to try and figure out how some elements of the Membrane RTC Engine work. I won't go into the details, but suffice to say this is a foreign code base to me, and it wasn't clear from the get go:So I was poking around blindly until I got my RTC Engine's process's graphed with Kino. This is what it looked like for reference:
Cool! So now I get to see the process layout, but I'm still blind as to what all this actually is. I still don't know what Membrane is doing. To get a bit more insight, changed the label for the PID node to also print out the node's id and got this:
This helped me relate my WebRTC endpoints with pid's and I also really like the insight it gives when you plot a Phoenix app's supervision tree.