summaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorDavid Goulet <dgoulet@torproject.org>2021-12-13 10:44:24 -0500
committerDavid Goulet <dgoulet@torproject.org>2021-12-13 10:49:00 -0500
commitbf1ed5c8534c515bf1ee39bfbf8c340d704b4490 (patch)
treec41e7da0c098fa65d3a62bb510864353971b2953 /changes
parentad6a0ebb119dba09fd1a0d1d6eb2a1362803bce3 (diff)
downloadtor-bf1ed5c8534c515bf1ee39bfbf8c340d704b4490.tar.gz
tor-bf1ed5c8534c515bf1ee39bfbf8c340d704b4490.zip
relay: Change DNS timeout label on MetricsPort
Change it from "timeout" to "tor_timeout" in order to indicate that the DNS timeout is one from tor's DNS threshold and not the DNS server itself. Fixes #40527 Signed-off-by: David Goulet <dgoulet@torproject.org>
Diffstat (limited to 'changes')
-rw-r--r--changes/ticket405276
1 files changed, 6 insertions, 0 deletions
diff --git a/changes/ticket40527 b/changes/ticket40527
index 631b3d4bb9..25bf6c57e3 100644
--- a/changes/ticket40527
+++ b/changes/ticket40527
@@ -3,3 +3,9 @@
timeouts are different from DNS server timeout. They have to be seen as
timeout related to UX and not because of a network problem. Fixes bug
40527; bugfix on 0.4.6.1-alpha.
+ - Change the MetricsPort DNS "timeout" label to be "tor_timeout" in order
+ to indicate that this was a DNS timeout from tor perspective and not the
+ DNS server itself.
+ - Deprecate overload_dns_timeout_period_secs and
+ overload_dns_timeout_scale_percent consensus parameters as well. They
+ were used to assess the overload state which is no more now.