This message was deleted.
# helpdesk
s
This message was deleted.
b
also I can’t really follow these numbers and squares: a.) what is the the resolution above the arrows suppoed to be (I don’t know how it correlates with the resolution in the hover menu) b.) how can I see which additional layers where simulcasted, is this the content of the hover dialog? d.) what exactly do the dimensions and timings in the hover dialog mean and what do the arrows and squares stand for? e.) why do I only have some of the time covered by Dimensions when the camera was enabled during the whole call as you can see in the bitrate diagram above it?
maybe a bit of context: We are running livekit on our servers based on the OOS solution but have found that analyzing quality problem reports is really hard if you don’t have a good analytics UI. This is why we have temporarily switched to the official LiveKit cloud for one of our instances to see how good the analytics capabilites are. I think they analytics features are pretty good but I’d additionally be interested in things like • which simulcast layers where published • when did simulcast layers stop publishing / start publishing and why (congestion / dynacast / …) • which simulcast layer was subscribed • When did the subscribed layer change and why
a
Good eye — I just fixed this and it’ll go out in today’s deploy. In general, thanks for the feedback on this visualization — yeah, it’s confusing and we’ve been meaning to revamp it. (As you’ve observed, the design really breaks down in the complex debugging cases, which are the ones where you really care.) Incidentally, would you have any interest in an analytics product that plugged in to your OSS instance? ie, you run your own deployment of livekit OSS, which exports data to our cloud-hosted analytics product?
👍 1
b
Incidentally, would you have any interest in an analytics product that plugged in to your OSS instance?
Yes! 100%! (I work with @best-parrot-43500)
b
Thanks for your answer@acoustic-engineer-41666! Like @billowy-apple-14314 says we’d be very happy to use your analytics for our OSS instance! We’d also be happy to contribute in any way if possible. We don’t see the point in starting to build our own analytics on top of your OSS stack if we could join forces and help you guys improve your analytics.