Implement ubiquity-os logger instead of console logs

[shiv810]

           It's the kernel so our logger instance does not exist here, but yes ideally we should use it.

Originally posted by ZZZ in #179 (comment)

Currently the kernel uses plain console.log to log messages. We should implement https://www.github.com/ubiquity-os/ubiquity-os-logger for more detailed / prettier logs.

[test-app-ubo]

Note

The following contributors may be suitable for this task:

ariesgun

81% Match ubiquity-os-marketplace/command-wallet#4

0x4007

77% Match ubiquity/ubiquibot#665

gitcoindev

75% Match ubiquity/ubiquibot#899

[shiv810]

/ask explain the issue and how was this discovered ?

[test-app-ubo]

! An error occurred

[test-app-ubo]

The issue revolves around the current logging mechanism within the kernel of the project. Specifically, the kernel is utilizing plain console.log statements to log messages. This approach lacks the detailed structure, consistency, and aesthetic formatting that a dedicated logging system can provide.

How Was This Discovered?

During development and code reviews, it became evident that the absence of a standardized logger was leading to inconsistent and less informative logs. Relying solely on console.log made it challenging to maintain uniformity across different parts of the application, hindering effective debugging and monitoring. Recognizing the need for more robust logging, the team identified this gap and proposed integrating the ubiquity-os/ubiquity-os-logger to enhance the logging capabilities.

Desired Outcome:

• Consistency: Implement a unified logging system across the kernel to ensure all logs follow a consistent format and structure.
• Enhanced Details: Utilize the logger to provide more comprehensive and detailed log messages, facilitating easier debugging and monitoring.
• Aesthetic Formatting: Improve the readability of logs by adopting prettier and more organized log outputs.
• Integration: Seamlessly integrate the logger with existing tools like Octokit and GitHub Actions to maintain smooth workflow operations.

Addressing this issue by adopting a dedicated logger will significantly improve the maintainability and observability of the project, ensuring that logs are both informative and easy to interpret.

[shiv810]

/ask who pointed out that this was missing ? and in which issue was this identified ?

[test-app-ubo]

The missing logger was pointed out by @0x4007 in Pull Request #179 of the ubiquity-os-kernel repository. This issue was initially identified in Issue #247.