Hi,
New here, so I might be off. I have created 2 Ingresses with the live-server-sdk. When I stream to these Ingresses, the page https://cloud.livekit.io/projects/p_xxxxxxxx/ingresses shows 10 ingresses, each of which have the same value (seem duplicates. Am I missing something?
Your help is appreciated!
@luc.stakenborg, Ingresses are persistent, reusable resources, not per-stream objects: once created, an ingress “remains valid, in a disconnected state, allowing it to be reused with the same stream key” (ingress overview). CreateIngress makes a new one on every call, so if your code runs it per stream, per reconnect, or on each app start, you accumulate identical copies, which is what those 10 look like.
Confirm it with ListIngress: if it returns 10, they are real resources your code created, so DeleteIngress the extras and create each ingress once, then reuse its url and stream_key for later streams. If ListIngress returns your 2 but the dashboard still shows 10, that is a display issue on the page.
There is a lot wrong with your dashboard view (only one of your Ingresses is shown, start times are all the same, durations do not sum to the session durations, sessions lack a room ID).
I thought this was perhaps a dashboard issue, but a random sample of other projects showed that this is isolated only to your specific project.
I can see only one call to CreateIngress in the server logs for each of the 2 Ingresses you created. I see multiple participant sessions created for each of those Ingresses, is that intentional? Multiple users joining that stream? The first thing I would try is to establish a single Ingress with an OBS client to isolate the client away from your workflow, and any potential stream reuse.
Hi, thanks for your reply.
I have created 2 ingress endpoints with the server-sdk. This is confirmed by ListIngress. I am using ffmpeg to stream a WHIP stream to the ingress points. I have (sequentially) initiated streams to one Ingress endpoint (one running at a time). I can see the streams start and stop in the room and all seems well, except the dashboard pages (ingresses and sessions). Am I missing something?
I assume I can re-use a ingress endpoint, because it is persistent? This worked for me on earlier trials.
You’re not missing something, this looks like a dashboard bug to me.
Thank you for raising this, I have raised it internally
