You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 11, 2024. It is now read-only.
As you can see, it expects XML events files. I added some logging to waagent2.0 to see what is going on, and it's receiving XML files for all of the event files that other providers place in /var/lib/waagent/events/, except the OmsAgent files are all JSON and cause errors.
I should note that this issue seems to be caused by my patch for Azure/WALinuxAgent#1550 . In that patch, I'm using waagent2.0, which causes this. I wasn't aware that waagent2.0 is older code than waagent (because it wasn't documented anywhere).
Thank you for your submission. As previously announced, the Log Analytics agent has been deprecated and has no support as of August 31, 2024. If you use the Log Analytics agent to ingest data to Azure Monitor, migrate now to the new Azure Monitor agent. As part of repo archival, open issues and pull requests will be closed.
I keep seeing these errors from the walinuxagent service:
The source for the waagent file (CollectAndSendWalaEvents) is here:
https://github.com/Azure/WALinuxAgent/blob/v2.2.40/bin/waagent2.0#L4902
As you can see, it expects XML events files. I added some logging to
waagent2.0
to see what is going on, and it's receiving XML files for all of the event files that other providers place in/var/lib/waagent/events/
, except the OmsAgent files are all JSON and cause errors.For example (addition of logging is mine):
The text was updated successfully, but these errors were encountered: