mirror of
https://github.com/pi-hole/docs.git
synced 2026-02-15 07:26:03 +00:00
Merge pull request #49 from pi-hole/new/FTL-config-update
Update FTL documentation
This commit is contained in:
@@ -55,7 +55,7 @@ Up to how many hours of queries should be imported from the database and logs? M
|
||||
On which port should FTL be listening?
|
||||
|
||||
### PRIVACYLEVEL
|
||||
`PRIVACYLEVEL=0|1|2|3`
|
||||
`PRIVACYLEVEL=0|1|2|3|4`
|
||||
|
||||
Which privacy level is used?
|
||||
|
||||
@@ -82,5 +82,12 @@ Controls if *FTL*DNS should print extended details about regex matching into `pi
|
||||
|
||||
**[More details](regex/overview.md)**
|
||||
|
||||
### DBIMPORT
|
||||
`DBIMPORT=yes|no`
|
||||
|
||||
Should `FTL` load information from the database on startup to be aware of the most recent history?
|
||||
|
||||
**[More details](database.md)**
|
||||
|
||||
|
||||
{!abbreviations.md!}
|
||||
|
||||
@@ -15,6 +15,8 @@ Note that DNS resolution will not be available as long as `pihole-FTL` is stoppe
|
||||
|
||||
Another way of controlling the size of the long-term database is setting a maximum age for log queries to keep using the config parameter [`MAXDBDAYS`](configfile.md#maxdbdays). It defaults to 365 days, i.e. queries that are older than one year get periodically removed to limit the growth of the long-term database file.
|
||||
|
||||
The config parameter [`DBIMPORT`](configfile.md#dbimport) controls whether `FTL` loads information from the database on startup. It need to do this to populate the internal datastructure with the most recent history. However, as importing from the database on disk can delay FTL on very large deploys, it can be disabled using this option.
|
||||
|
||||
---
|
||||
|
||||
The long-term database contains three tables:
|
||||
|
||||
@@ -23,8 +23,8 @@ This setting disables
|
||||
- Top Clients
|
||||
- Clients over time
|
||||
|
||||
### Level 3 - paranoia mode (hide everything)
|
||||
Disabled basically everything except the most anonymous statistics
|
||||
### Level 3 - anonymous mode (anonymize everything)
|
||||
Disable all details except the most anonymous statistics
|
||||
|
||||
This setting disables
|
||||
|
||||
@@ -35,4 +35,8 @@ This setting disables
|
||||
- Query Log
|
||||
- Long-term database logging
|
||||
|
||||
### Level 4 - disabled statistics
|
||||
Disables all statistics processing. Even the query counters will not be available.
|
||||
Additionally, you can disable logging to the file `/var/log/pihole.log` using `sudo pihole logging off`.
|
||||
|
||||
{!abbreviations.md!}
|
||||
|
||||
Reference in New Issue
Block a user