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
Hello, I have in home several devices, some of then I want to maintain logging but others simply introduce a lot of entries and I want to exclude this devices from my Query Log.
For example, all my Voip phones check a lot the configured SIP servers, and the NTP servers, this type of info is irrelevant for my query log, and simply make the log too long for audit.
Another example is my piAware device, this device check every 5-10 seconds "pfclient-upload.planefinder.net", when I try to see my log for check someting result impossible without filtering, but filtering is slow.
Should be good if I can select my voip devices, and my Piaware devices for use my DNS server but not logging at all.
Please could you consider this in a near release?
Thanks in advance.
José
The text was updated successfully, but these errors were encountered:
For example, all my Voip phones check a lot the configured SIP servers, and the NTP servers, this type of info is irrelevant for my query log, and simply make the log too long for audit.
Hello, I have in home several devices, some of then I want to maintain logging but others simply introduce a lot of entries and I want to exclude this devices from my Query Log.
For example, all my Voip phones check a lot the configured SIP servers, and the NTP servers, this type of info is irrelevant for my query log, and simply make the log too long for audit.
Another example is my piAware device, this device check every 5-10 seconds "pfclient-upload.planefinder.net", when I try to see my log for check someting result impossible without filtering, but filtering is slow.
Should be good if I can select my voip devices, and my Piaware devices for use my DNS server but not logging at all.
Please could you consider this in a near release?
Thanks in advance.
José
The text was updated successfully, but these errors were encountered: