This message was deleted.

hi @high-quill-15727, nice to meet you! 🙂 This might be helpful: https://docs.livekit.io/realtime/client/data-messages/#data-messages

@magnificent-art-43333 thank you for your reply. This may be a basic question, but please let me know. We understand that LikeKit corresponds to the SFU server. Looking at the document, there is an implementation example for the client and server (probably the SFU server), but in addition to that, is it necessary to separately implement the STUN/TURN server and signaling server, which are familiar to WebRTC? Or is the signaling server functionality also included in LiveKit? https://docs.livekit.io/realtime/

Hey @high-quill-15727, all of what you mention are part of LiveKit. It's an end-to-end WebRTC stack. You can get started with one of our client SDKs (checkout the quickstarts)

@dry-elephant-14928 Thank you for your reply. I see, I understand. It's great that everything is included. Try using the quick start as a reference. I would be happy if I could ask you another question.

feel free to ask away @high-quill-15727 🙂

@dry-elephant-14928 @magnificent-art-43333 Sorry, please ask me again. Is it possible to output communication logs for LiveKit functions? I would like to be able to check the error details in the log when the WebRTC connection fails.

Yeah, you can configure the log level of the internal logger

@dry-elephant-14928 thank you for your reply. As an image, is it possible to output logs to a file or externally on the SFU server? I would be grateful if you could provide me with any configuration samples or documentation.