mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
Add support for remote logging #5022
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#5022
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mfbloom on GitHub (Jan 22, 2024).
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to request a feature or enhancement and not ask a question
The problem
DNS query results are only stored via QueryLog to a file, and there is no current method to ship the logs remotely to an external system.
Proposed solution
Give users the ability to remotely ship logs via TCP or UDP. Users will have the ability to update these settings from the UI under the General -> Logs configuration section.
In this section, the user will be able to specify if remote logging is enabled/disabled, the endpoint/port of the remote host, and the protocol to utilize (UDP/TCP). Additionally, users will be provided limited options in how the message will be formatted and the fields that can be included. This will be written so it can be expanded easily in the future.
Alternatives considered and additional information
A separate logging system could be utilized to retrieve the logs from disk. However, it would be beneficial to have the option to ship the logs directly.
I have started writing the code and am almost ready for a PR.
@ainar-g commented on GitHub (Jan 23, 2024):
Merging into #4233, if you don't mind.
The current query logging code is not the best and will probably be replaced for v0.108, see #2290. This is also a big feature that sounds like it would need a lot of support, and most users won't have use for it, so I want to be honest and say that the possibility of merging it in the near future is not that high.