mirror of
https://github.com/chr0nzz/traefik-manager.git
synced 2026-05-09 05:35:22 +02:00
[GH-ISSUE #27] Feature: Ability to filter by EntryPoint, Middleware, Services in the Route Map page #26
Labels
No labels
bug
bug
bug
feature request
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/traefik-manager#26
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 @counterf on GitHub (Apr 18, 2026).
Original GitHub issue: https://github.com/chr0nzz/traefik-manager/issues/27
Originally assigned to: @chr0nzz on GitHub.
The route map page is awesome, it makes it easy to visualize all the different routes. By hovering the mouse over the route, the map automatically filters entrypoint, middleware and service associated with it.
It is not possible, however, to hover the mouse over an entrypoint, and get the same view, with routes, middlewares and services filterered to that entrypoint.
Use case: Traefik-manager identified an entrypoint that I was not aware, but I have too many routes and it is hard to figure out, via map, what routes are related to that Entrypoint.
I am also curious to know what routes are NOT using a specific middleware. I cannot easily answer these questions via the route map.
@chr0nzz commented on GitHub (Apr 18, 2026):
Thanks for the suggestion! This is a great idea - the current hover behavior is one-directional (route -> connected nodes) and making it symmetric makes a lot of sense, especially for the use case you described.
This will be implemented in the upcoming v1.0.0 release. Hovering any entrypoint, middleware, or service node will highlight all connected routes and bring them into alignment - same visual behavior as hovering a route today.
@chr0nzz commented on GitHub (Apr 19, 2026):
v1 beta 1 is out if u wanna test it
https://beta-tm.xyzlab.dev
@counterf commented on GitHub (Apr 20, 2026):
The beta install script seems to be limited to docker installs. are you not support systemd installs?
@chr0nzz commented on GitHub (Apr 20, 2026):
if you chose to install traefik + traefik manager it will install in docker
if you chose to install traefik manager only you have an option to pick docker or systemd
@counterf commented on GitHub (Apr 20, 2026):
okay, so I got beta installed on my linux LXC
Few things:
I am wondering if I am actually running the beta version. I suspect the beta install script is somehow using the latest 0.X release.
@chr0nzz commented on GitHub (Apr 20, 2026):
it should show v1.0.0-beta1 if you are on the beta img.
are you using docker? if so is the image: ghcr.io/chr0nzz/traefik-manager:beta or using the :latest?
if you are using systemd Linux - I made a mistake and forgot to point the cloning to the v1 beta branch. Run it again, I've updated it.
@counterf commented on GitHub (Apr 20, 2026):
I got the beta installed now. Thanks!
One thing Id suggest for systemd installs is to tune the script for these installs. This part of the script is probably not needed for systemd installs. It asks for container name (no container in systemd installs).
---- snippet from install on lxc traefik
-- Static Config Editor --
ℹ Choose how TM should restart Traefik after saving static config changes.
Restart method
1) Poison pill (recommended - signal file, no Docker socket needed)
2) Direct Docker socket (requires TM user to have Docker group access)
Choice [1]: 1
Traefik container name [traefik]: traefik-internal
Signal file path [/var/lib/traefik-manager/signals/restart.sig]: /opt/traefik/restart.sig
@chr0nzz commented on GitHub (Apr 20, 2026):
the script now handles how traefik is run and will provide the correct setup.
https://github.com/chr0nzz/traefik-manager/releases/tag/v1.0.0-beta1.1
@counterf commented on GitHub (Apr 20, 2026):
The page breaks when I move the mouse over an entrypoint with many routes.
When there is 1 to many relationship, the page breaks.
@chr0nzz commented on GitHub (Apr 20, 2026):
Can u press f12 and take a screenshot of the errors u see in the console.
@counterf commented on GitHub (Apr 20, 2026):
There is no error there. This is not really a functional error. It is more of a layout / visualization limitation in the Route Map interaction logic. The page is doing what it thinks it thinks it needs to do.
The Route Map behaves well when highlighting a router, because a single router usually maps to a manageable number of middlewares and services. In that case, re-aligning related nodes works nicely.
The problem appears when highlighting an entrypoint or a middleware that is connected to many routers. The current layout logic tries to vertically align all related routers around the selected entrypoint or middleware. When there are too many related routers, some are pushed above the visible canvas area, including into the page header region, so they become partially or fully hidden. As a result, it is not possible to see all routers associated with that entrypoint or middleware.
Why this happens
The visualization strategy that works well for router-focused exploration does not scale well for entrypoints or middlewares with many router connections. Instead of preserving visibility, the map centers the linked routers around the selected node, which can push part of the graph outside the visible area.
Actual behavior
Hovering an entrypoint or middleware connected to many routers causes the related routers to be repositioned vertically around that node. If there are enough routers, some are rendered outside the visible map area and get cut off near the top of the page.
Expected behavior
All related routers should remain visible when highlighting an entrypoint or middleware, even when there are many of them. The map should avoid positioning nodes outside the visible canvas.
Possible improvements
Instead of centering all linked routers around the selected entrypoint or middleware, the UI could:
-constrain repositioning to the visible canvas
-add scroll/pan support for overflowed nodes
-reduce or disable aggressive re-alignment when too many routers are linked
-use a different highlight mode for high-fanout nodes like entrypoints and middlewares
@chr0nzz commented on GitHub (Apr 20, 2026):
please update
https://github.com/chr0nzz/traefik-manager/releases/tag/v1.0.0-beta1.2
@counterf commented on GitHub (Apr 20, 2026):
@chr0nzz commented on GitHub (Apr 21, 2026):
working on fix will be out in the next beta release
@chr0nzz commented on GitHub (Apr 22, 2026):
please update to beta2 and let me know if it fixes the issues. thanks for all the feedback
@counterf commented on GitHub (Apr 22, 2026):
Almost there. If i move mouse over the routes, any route without middleware gets a line over the middleware. It is just a cosmetic issue
@chr0nzz commented on GitHub (Apr 26, 2026):
please check beta3 with new and improved route map and please let me know how its working for you. thanks
@counterf commented on GitHub (Apr 26, 2026):
just played with it. I liked it
I dont see any issues.