AdguardTeam / AdguardTeam/AdGuardHome

Upstream Hyperlinks

Offen
#8,203 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
feature request
Vorherrschende Sprache
TypeScript
Sterne
36.9k
Forks
2.5k
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

### Prerequisites

- [x] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions) and found no answer

- [x] I have searched other issues and found no duplicates

- [x] I want to request a feature or enhancement and not ask a question

### The problem

Once in a while I see a very high "Average stream response time" for one of the upstream servers, mostly the gateway. It is always a painful time-consuming task to scroll page after page, visually scanning for the culprit. Usually it is some bogus name that the router issues to test communication with the outside, which obviously does not get resolved, yet it takes a very long time to process. I wish there was a quick way to locate such entries.

### Proposed solution

If you would add hyperlinks in the "Top Upstreams" and "Average Upstream Response Time" sections, like you do in all the other sections, we could simply click on the hyperlink for the upstream server reporting very high response times, to return a much narrower list and quickly find the culprit.

### Alternatives considered and additional information

Manually scrolling, hoping I don't visually miss the one entry among thousands.

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.