New Issue

Add timestamps to console messages #641

Open

opened by GitHubGeek · 1 comments

GitHubGeek commented (Migrated from github.com)

Is your feature request related to a problem? Please describe.
When running ~/.cargo/bin/plume, the output messages have no timestamps, making it a bit harder to check for issues.

Describe the solution you'd like
All console messages should be prefixed with timestamps

Describe alternatives you've considered
n/a

Additional context
n/a

**Is your feature request related to a problem? Please describe.** When running `~/.cargo/bin/plume`, the output messages have no timestamps, making it a bit harder to check for issues. **Describe the solution you'd like** All console messages should be prefixed with timestamps **Describe alternatives you've considered** n/a **Additional context** n/a

👍 1

elegaanz commented (Migrated from github.com)

If you use systemd (at least, maybe other init system do it to), the date and time are logged in journalctl normally (but I agree that the timestamp should be here without having to run plume with a specific init system).

If you use systemd (at least, maybe other init system do it to), the date and time are logged in `journalctl` normally (but I agree that the timestamp should be here without having to run plume with a specific init system).

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Loading…

There is no content yet.

Labels Milestones

Add timestamps to console messages #641