aefdba0144
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. https://github.com/Azure/azure-extension-platform/pull/34 |
||
|---|---|---|
| .. | ||
| cmds.go | ||
| cmds_test.go | ||
| constants.go | ||
| handlersettings.go | ||
| handlersettings_test.go | ||
| health.go | ||
| health_test.go | ||
| main.go | ||
| probeResponse.go | ||
| reportstatus.go | ||
| reportstatus_test.go | ||
| schema.go | ||
| schema_test.go | ||
| seqnum.go | ||
| status.go | ||
| version.go | ||
| version_test.go | ||
| vmWatch.go | ||
| vmWatch_test.go | ||