You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The machines on my network all have short, memorable, well-known names. I want to use these names to browse the query log but the query log filter only inspects literal fields of the json log entries.
Proposed Solution
Host names used as query log filters are checked through the known client directory and, if found, the resultant query is OR of existing functionality and client IP.
Alternatives Considered
If resolution succeeds, ONLY the resolved IP is used for the filter.
Logs extended to include resolved client host names.
Support for logging to an external service like an ELK deployment.
The text was updated successfully, but these errors were encountered:
Problem Description
The machines on my network all have short, memorable, well-known names. I want to use these names to browse the query log but the query log filter only inspects literal fields of the json log entries.
Proposed Solution
Host names used as query log filters are checked through the known client directory and, if found, the resultant query is OR of existing functionality and client IP.
Alternatives Considered
The text was updated successfully, but these errors were encountered: