Skip to content
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

NGINXHTTPServer Parsers doesn't include information about the log source hostname. #10349

Closed
ecIib7L opened this issue Apr 19, 2024 · 8 comments
Assignees
Labels
feature request Parser Parser specialty review needed

Comments

@ecIib7L
Copy link

ecIib7L commented Apr 19, 2024

[Is your feature request related to a problem? Please describe.
NGINXHTTPServer Parsers doesn't include information about the log source hostname.

Describe the solution you'd like
Add the log source hostname to the parser for example: extend EventSource = ManagementGroupName

Describe alternatives you've considered

Additional context
https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/NGINX%20HTTP%20Server/Parsers/NGINXHTTPServer.txt

@v-sudkharat v-sudkharat added the Parser Parser specialty review needed label Apr 22, 2024
@v-sudkharat
Copy link
Contributor

Hi @ecIib7L, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 26-04-2024. Thanks!

@v-sudkharat
Copy link
Contributor

Hey @ecIib7L, Could you please check the below updated parser and let us know it resolve your issue?
Note : The ManagementGroupName is having same hostname as Computer, so you will get the same value for EventSource.
NGINX.txt

Please share the sample data with us if still you are not getting the log source hostname.
Thanks!

@ecIib7L
Copy link
Author

ecIib7L commented Apr 29, 2024

Hi @v-sudkharat I saw that the nginx_errorlog_events doesn't have EventSource contigured. Could you please also update this part? I think this will result in errors in the "union....project... EventSource" expression.
Yes this will resolve my issue. I will update this for our directories when this is pushed to the content hub.

@v-sudkharat
Copy link
Contributor

@ecIib7L, We have just updated the parser, could you please check it into your available data and let us know if it running correctly?
NGINX.txt

Please share the parser successfully running result screenshot over here or this mail id - v-sudkharat@microsoft.com
So, we can procced to update this into content hub. Thanks!

@ecIib7L
Copy link
Author

ecIib7L commented Apr 29, 2024

Hi @v-sudkharat Yes, the parser seems working for both access logs and error logs:
image

@v-sudkharat
Copy link
Contributor

@ecIib7L, thanks for the update. we will finalize it and proceed to raise PR. Could you please let us know can we close this issue from GitHub.
Thanks!

@ecIib7L
Copy link
Author

ecIib7L commented Apr 29, 2024

@v-sudkharat Sure, you can close this issue. Thanks for your help.

@v-sudkharat
Copy link
Contributor

Thanks for confirmation. Closing this issue. If you still need support for this issue, feel free to re-open it any time. Thank you for your co-operation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Parser Parser specialty review needed
Projects
None yet
Development

No branches or pull requests

3 participants