feat: Show microsecond precision in journald logs#17
Open
Bravo555 wants to merge 1 commit intothin-edge:mainfrom
Open
feat: Show microsecond precision in journald logs#17Bravo555 wants to merge 1 commit intothin-edge:mainfrom
Bravo555 wants to merge 1 commit intothin-edge:mainfrom
Conversation
Use the [`short-precise`](https://www.freedesktop.org/software/systemd/man/latest/journalctl.html#short-precise) output option to show timestamp up to microsecond precision in journald logs. I am debugging an issue where my hypothesis is that after tedge-mapper-c8y is stopped in the test and the test uses Cumulocity library to delete devices, Cumulocity might still respond to in-flight MQTT messages, which may create devices after I've deleted them. However, logs from MQTT messages and tedge-mapper-c8y have sub-second precision, but from mosquitto do not, which is annoying because mosquitto reports when we receive Cumulocity PUBACKs. This option enables sub-second precision for these logs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use the
short-preciseoutput option to show timestamp up to microsecond precision in journald logs.I am debugging an issue where my hypothesis is that after tedge-mapper-c8y is stopped in the test and the test uses Cumulocity library to delete devices, Cumulocity might still respond to in-flight MQTT messages, which may create devices after I've deleted them.
However, logs from MQTT messages and tedge-mapper-c8y have sub-second precision, but from mosquitto do not, which is annoying because mosquitto reports when we receive Cumulocity PUBACKs. This option enables sub-second precision for these logs.