-
Notifications
You must be signed in to change notification settings - Fork 444
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
[IIS] Update document with supported ingest patterns for access_log
#6892
Conversation
🌐 Coverage report
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please refer to this: https://www.crowdstrike.com/cybersecurity-101/observability/iis-logs/
Did we miss a format (see the blog by Crowdstrike)? And can we elaborate on some points like in this blog? Also, we have not referenced any official document or so. Please add some links so that users can cross-check what's written here.
access_log
Did you check this comment: #6892 (review)? |
You mean the log format like W3C, We have captured the supported log formats in the document already. Its not necessary to cover the logging formats what IIS provides in detail as of now as we don't support them right now. We have the IIS logging official document link included. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
Package iis - 1.14.0 containing this change is available at https://epr.elastic.co/search?package=iis |
What does this PR do?
The IIS access_log provides flexibility for the customer to edit the default logging fields and add new fields. The IIS integration currently supports the default and a few custom selections. The supported patterns are captured in the document.
How to test this PR locally
Verify the documentation in the access_log section and make sure that the supported patterns are captured.
Related issues