-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vCenter Parser: Error in parsing events of type UserEventsLogoutEvent when the value of "number of API invocations" within the raw event message is not an integer. #11542
Comments
Hi @kevintamlsWork, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates. Thanks! |
@kevintamlsWork, could you please share the sample logs with us on mail id - [email protected] Thanks! |
Hi @v-sudkharat, just sent a selection to your email. Do let me know if you'd like further information or clarifications. Thanks. |
@kevintamlsWork, Received the mail, Will investigate on it and get back to you with some updates. Thanks! |
@v-sudkharat Thank you, will await you response. Thanks. |
Hi @kevintamlsWork, Thanks for sharing the RAW logs which help us to address this issue.
Thanks! |
@v-sudkharat that has worked for this specific parsing issue. However, we are encountered another parsing issue separate from this issue. Shall I keep using this issue or open a new one? Thanks |
@kevintamlsWork, Could you please share what new issue your facing? and it's due to the above shared parser or it due to the any filed not parsing correctly? |
@v-sudkharat It's not related to the above shared parser, this issue affects both Login and Logout events and results in all fields not being parsed correctly. This issue affects the original parser also so is unrelated to the shared parser above. Describe the bug
To Reproduce
vCenterV2
Expected behavior Screenshots Working: Not working: Sample logs below, do let me know if you would like more in an email alongside a more detailed description of the issue, I have put the areas we think may be the cause of the issue in Bold and Italics. OS, and browser used are the same. Login Events Not Working Dec 18 14:36:56 SERVERNAME vpxd[7058] Event [50297246] [1-1] [2024-12-18T14:36:47.241233Z] [vim.event.UserLoginSessionEvent] [info] [username] [xxx] [50297246] [User userName@xxx.xxx.xxx.xxx logged in as VMware-client/6.5.0] Working Dec 19 10:30:27 SERVERNAME vpxd[7058] Event [50319750] [1-1] [2024-12-19T10:30:27.644457Z] [vim.event.UserLoginSessionEvent] [info] [domainName\userName] [] [50319750] [User domainName\userName@xxx.xxx.xxx.xxx logged in as VMware vim-java 1.0] Logout Events Not Working Dec 19 10:41:18 SERVERNAME vpxd[7058] Event [50319923] [1-1] [2024-12-19T10:41:00.843279Z] [vim.event.UserLogoutSessionEvent] [info] [username] [xxx] [50319923] [User userName@xxx.xxx.xxx.xxx logged out (login time: Thursday, 19 December, 2024 10:10:30 AM, number of API invocations: 6, user agent: VMware-client/6.5.0)] Working Dec 19 09:50:02 SERVERNAME vpxd[7058] Event [50319033] [1-1] [2024-12-19T09:50:02.514923Z] [vim.event.UserLogoutSessionEvent] [info] [domainName\userName] [] [50319033] [User domainName\userName@xxx.xxx.xxx.xxx logged out (login time: Thursday, 19 December, 2024 09:50:02 AM, number of API invocations: 1, user agent: Apache-CXF/3.4.10)] |
@kevintamlsWork, Ok, let us investigate on it. |
@v-sudkharat Thank you, much appreciated. |
@kevintamlsWork, the Parser not parsing the below RAW format -
And
|
@v-sudkharat yes sure
|
@kevintamlsWork, Updated the below parser to meet your requirements: - Could you please test and let us know if it meets the results:
|
@v-sudkharat Will do, do expect a reply after Christmas though as I will be busy over it :) |
Describe the bug
The vCenter Parser fails to parse events of type UserEventsLogout when the value of "number of API invocations" within the raw event message is not an integer.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Events that contain a comma within the APIInvocationCount field to be parsed correctly in all fields.
Screenshots
Some values of fields within events has been redacted.
Working:
Not Working:
Desktop (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: