-
Notifications
You must be signed in to change notification settings - Fork 392
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
[microsoft_dhcp] Add DHCP qresult descriptions #7207
Conversation
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.
Should this be added to DHCPv6 as well?
packages/microsoft_dhcp/data_stream/log/elasticsearch/ingest_pipeline/dhcp.yml
Outdated
Show resolved
Hide resolved
/test |
🌐 Coverage report
|
…ipeline/dhcp.yml Co-authored-by: Dan Kortschak <90160302+efd6@users.noreply.github.com>
Co-authored-by: Dan Kortschak <90160302+efd6@users.noreply.github.com>
I didn't have any DHCPv6 logs indicating that this would align with them. |
/test |
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.
Thanks
Package microsoft_dhcp - 1.18.0 containing this change is available at https://epr.elastic.co/search?package=microsoft_dhcp |
Currently the QResult is stored in the event logs as a number which is usually 6 or 0 which will mean nothing to the end user if they don't understand the correlation. This change will add a new field called microsoft.dhcp.result_description to events based on that numerical value of the quarantine result. The event logs contain the mapping for this data and cannot be found in Microsoft's official documentation. This is from the DHCP event log when it gets created (Notice the QResult Line): ...snipped for brevity... 34 DNS update request failed.as the DNS update request queue limit exceeded. 35 DNS update request failed. 36 Packet dropped because the server is in failover standby role or the hash of the client ID does not match. 50+ Codes above 50 are used for Rogue Server Detection information. QResult: 0: NoQuarantine, 1:Quarantine, 2:Drop Packet, 3:Probation,6:No Quarantine Information ProbationTime:Year-Month-Day Hour:Minute:Second:MilliSecond. ID,Date,Time,Description,IP Address,Host Name,MAC Address,User Name, TransactionID, QResult,Probationtime, CorrelationID,Dhcid,VendorClass(Hex),VendorClass(ASCII),UserClass(Hex),UserClass(ASCII),RelayAgentInformation,DnsRegError. 24,07/28/23,00:00:52,Database Cleanup Begin,,,,,0,6,,,,,,,,,0
What does this PR do?
Today the QResult is stored in the event logs as a number which is usually 6 or 0 which will mean nothing to the end user if they don't understand the correlation.
This PR will add a new field called
microsoft.dhcp.result_description
to events based on that numerical value of the quarantine result. The event logs contain the mapping for this data and cannot be found in Microsoft's official documentation.This is from the DHCP event log when it gets created (Notice the QResult Line):
The mappings are as follows:
Checklist
changelog.yml
file.