Open Issues Need Help
View All on GitHubAI Summary: This issue requests a reduction in log verbosity for `blueapi`, specifically targeting frequent `GET /healthz` messages and event messages, both currently logged at INFO level. The user proposes either removing these logs entirely or, at minimum, downgrading them to DEBUG level to improve log clarity and focus on more critical information.
AI Summary: The task is to eliminate duplicate logging of incoming requests in the blueapi application. This involves either disabling uvicorn's built-in access logging or removing the custom `log_request_details` method and implementing alternative filtering to log only necessary Kubernetes probe requests at the debug level. The goal is to prevent excessive logging of liveness/readiness probes while maintaining request logging for other endpoints.
AI Summary: Implement a check in BlueAPI's initialization to verify the configured STOMP address is reachable. If the address is unreachable, log a warning or error message indicating the failure. This will prevent situations where BlueAPI fails silently due to misconfiguration of the message broker.