You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to troubleshoot Oura configurations running via a systemd service in daemon mode, there is little to nothing in the way of messages printed to stdout that can be observed from common tools such as journalctl or the terminal window.
I propose that it would be helpful to add a configurable toggle of debugging-relevant information that could be printed to stdout in order to observe the status of the Oura instance in daemon mode.
Examples of useful information:
Connection to node/socket success/failure
Synchronization status
Webhook timeouts or other sink errors
The text was updated successfully, but these errors were encountered:
When attempting to troubleshoot Oura configurations running via a systemd service in daemon mode, there is little to nothing in the way of messages printed to stdout that can be observed from common tools such as journalctl or the terminal window.
I propose that it would be helpful to add a configurable toggle of debugging-relevant information that could be printed to stdout in order to observe the status of the Oura instance in daemon mode.
Examples of useful information:
The text was updated successfully, but these errors were encountered: