-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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: Hostname not being extracted #11642
Comments
Hi @kevintamlsWork, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates. Thanks! |
@kevintamlsWork, Updated the Parser by adding the Hostname in it, Could you please test and let us know is it working for you :
Thanks! |
@v-sudkharat Working well for most events, except for selected events in the form.
Working fine log format:
The parser is capturing everything after the initial timestamp as the hostname, where expected behaviour is to capture the string value before "vpxd". In this case, it's "extserv-vc-01". Screenshot: |
@kevintamlsWork, actually, the RAW message format you shared is different from the following formats: is in a different format compared to the following: a. b. We checked the RAW message format of A and B to extract the hostname, which is located after the It appears that in the recent RAW message, from the So, if we proceed with making changes to extract the hostname from the RAW message :
then the parser may fail to extract the hostname from the following raw message format:
Hope this information helps. Thanks! |
Describe the bug
The vCenter parser does not extract the hostname of the vCenter Syslog.
To Reproduce
Steps to reproduce the behavior:
vCenterV2
Expected behavior
Hostname (in the example below, VDIVCSA-P-01-01) should be extracted with a field name "Hostname"
Screenshots
Desktop (please complete the following information):
Additional context
We have had a modified version of the parser provided from issue#11542. If any modifications are required, please use the latest version of the modified parser from that issue.
Modified Parser Code
Syslog Message Example
The text was updated successfully, but these errors were encountered: