sometimes livekit and agent logs not swhown ın termınal although at livekit yaml log_level: debug ? why it happens sometimes ? @millions-hair-24956

It seems likely that the issue with Livekit and agent logs not showing in the terminal, despite setting

log_level: debug

in the Livekit YAML, could be related to how logging is configured or handled in your environment. According to the Livekit documentation, logging setup can be influenced by various factors, including the specific logging configuration in your application or any overrides that might be in place. My understanding is that you might want to ensure that the logging configuration is correctly set up in your application code as well. You can use the

setup_logging

function from the

livekit.agents.cli.log

module to explicitly set the logging level and ensure that logs are being captured and displayed as expected. Additionally, check if there are any conditions or filters in your code that might prevent certain logs from being displayed. Would you like more detailed guidance on setting up logging in your Livekit application? Sources: - Livekit documentation 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

so give me a prod ready setup order for best practice . i will have livekit -sip server- redis - and can i connect my agents to kubernetes with cı /cd or agents must be in kubernetes . give me best setup order . @millions-hair-24956

It seems likely that for a production-ready setup involving Livekit, SIP server, and Redis, you should consider deploying these components in a Kubernetes environment for scalability and management. According to the Livekit Kubernetes deployment guide, using Kubernetes allows you to leverage features like auto-scaling, load balancing, and easy updates via CI/CD pipelines. For best practices, you might follow this setup order: 1. Kubernetes Cluster Setup: Ensure you have a Kubernetes cluster ready, possibly on a cloud provider like AWS EKS, Google GKE, or Digital Ocean DOKS. Install Helm on your local machine for managing Kubernetes applications. 2. Deploy Redis: Deploy a Redis instance in your Kubernetes cluster. Redis is used as a shared data store and message bus for Livekit in a distributed setup. 3. Deploy Livekit: Use the Livekit Helm chart to deploy Livekit in your Kubernetes cluster. This setup will include configuring SSL certificates, setting up TURN servers, and ensuring the necessary ports are open. 4. Deploy SIP Server: Deploy your SIP server in the Kubernetes cluster. Ensure it is configured to communicate with Livekit and Redis. You can use a load balancer to manage SIP traffic. 5. CI/CD Integration: Set up a CI/CD pipeline to automate the deployment of your Livekit, SIP server, and Redis configurations. This can be done using tools like Jenkins, GitHub Actions, or GitLab CI/CD. 6. Agent Deployment: Agents can be deployed in Kubernetes using a similar CI/CD pipeline. You can connect your agents to Kubernetes, allowing them to scale with your infrastructure. According to the Livekit agents deployment guide, agents can be managed using Docker containers and orchestrated with Kubernetes. Would you like more detailed steps or examples for any specific part of this setup? Sources: - Livekit Kubernetes deployment guide - Livekit agents deployment guide 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.