Skip to content

Use RFC3339Nano for better timestamp precision in extension events#34

Merged
D1v38om83r merged 1 commit intoAzure:mainfrom
frank-pang-msft:dev/frankpang/improveLogging
May 21, 2024
Merged

Use RFC3339Nano for better timestamp precision in extension events#34
D1v38om83r merged 1 commit intoAzure:mainfrom
frank-pang-msft:dev/frankpang/improveLogging

Conversation

@frank-pang-msft
Copy link
Contributor

Extension events are currently in format RFC3339, which is in format yyyy-mm-ddThh:mm:ssZ. We should use RFC3339Nano instead so the logs can be sorted correctly with milliseconds/nanosecond precision.

Copy link
Contributor

@klugorosado klugorosado left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@D1v38om83r D1v38om83r merged commit 6b2acfd into Azure:main May 21, 2024
frank-pang-msft added a commit to Azure/applicationhealth-extension-linux that referenced this pull request May 21, 2024
Some info is missing in the kusto logs that are present in the local
logs that makes it difficult to debug.

- Log specific command being executed at startup
(install/enable/update/etc)
- Include extension sequence number and pid at startup for debugging
from GuestAgent logs when extension logs are missing or seqNum.status
file is missing
- Log overall status file so we have better debugging when
VMExtensionProvisioning fails. This status is only sent when extension
transitions between Transitioning -> Success/Error or whenever extension
starts up.
- Update azure-extension-platform package to pull in change to increase
precision of event timestamp to include milliseconds/nanoseconds,
Previously it was RFC3339, which is in format yyyy-mm-ddThh:mm:ssZ,
which causes issue in sorting timestamps.
Azure/azure-extension-platform#34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants