Repository navigation
[VMware] Add more vSphere/ESXi logs - #8122
Conversation
🌐 Coverage report
|
…t the end of the line
|
/test |
|
FYI I am on PTO from 4th November till 20th november. |
|
@philippkahr : There are some files for infoblox Integration. Was that added by mistake ? |
🚀 Benchmarks reportTo see the full report comment with |
|
@philippkahr I see that are still some unanswered review comments that were marked resolved without any action or comment on them. Can you please revisit or address those? This will help us close the review on this PR and approve the changes faster. Thanks |
Co-authored-by: Aman <38116245+devamanv@users.noreply.github.com>
|
@devamanv |
Co-authored-by: muthu-mps <101238137+muthu-mps@users.noreply.github.com>
That's fine, just wanted to make sure we were tracking the progress on this one. The changes look good. I will review the changes again once all the CI checks have passed and complete my part of the review. Thanks for addressing the review comments. |
|
@devamanv can you check the buildkite? I don't think that's on me. Since I didn't touch the govmomi go stuff. |
|
@philippkahr I have a hunch. Could you try to change the Go version to |
|
So, a plausible explanation of what could have caused the checks to fail is as follows: This in turn threw the following error: Note that I was able to see this error by adding the The uuid package recently added this change to support v7 of UUID. Finally, this implementation uses time.UnixMilli function, which was introduced in Go v1.17. So, the only option to fix this error was to upgrade the Go version. |
|
@philippkahr Now that we have updated the Go version, we might as well make another change to the
A similar change was done here in the vSphere module. |
Co-authored-by: Aman <38116245+devamanv@users.noreply.github.com>
|
/test |
|
Package vsphere - 1.10.0 containing this change is available at https://epr.elastic.co/search?package=vsphere |
Hi,
multiple things:
Since this is a bit more of a change. i am not sure that 1.9.0 is enough of a version bump, or if we want to go 2.0.0
See if it's possible to differentiate between ESXI and vsphere logs for event.dataset or something like this. I don't want to introduce a new datastream with:
logs-vsphere_esxi.log. Don't think that this is needed.figure out how to deal with multiline. It's not a JSON, not real KV as well. Bit weird to parse. Maybe try to parse only important stuff such as
eventTypeIdto ECS.Checklist
changelog.ymlfile.