starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Topology map does not limit to devices in the selected site #1075

New Issue
Closed
opened 2025-12-29 16:28:35 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:28:35 +01:00
Owner
Copy Link

Originally created by @candlerb on GitHub (Jul 6, 2017).

Issue type: bug?

Python version: 2.7.12
NetBox version: 2.0.8

When generating a topology map for a site, the devices shown are not filtered to the site selected.

For example, if you enter "rtr" as a pattern, then you get devices across all sites whose name includes substring "rtr", even if you have selected a single site for the topology map.

Is this intentional? The doc says:

Each topology map is associated with a site. A site can have multiple topology maps, which might each illustrate a different aspect of its infrastructure (for example, production versus backend infrastructure).

If the devices are not filtered to the selected site, then there seems to be little point in selecting a site - apart from the fact that it controls which maps are offered when you browse to /dcim/sites/<sitename>/

I suppose it might be intended to have an upstream device from another site shown in a site-specific topology map; but this can also be done with a global topology map (one which is not associated to a site)

Originally created by @candlerb on GitHub (Jul 6, 2017). ### Issue type: bug? **Python version:** 2.7.12 **NetBox version:** 2.0.8 When generating a [topology map](https://netbox.readthedocs.io/en/stable/data-model/extras/#topology-maps) for a site, the devices shown are not filtered to the site selected. For example, if you enter "rtr" as a pattern, then you get devices across all sites whose name includes substring "rtr", even if you have selected a single site for the topology map. Is this intentional? The doc says: > Each topology map is associated with a site. A site can have multiple topology maps, which might each illustrate a different aspect of its infrastructure (for example, production versus backend infrastructure). If the devices are not filtered to the selected site, then there seems to be little point in selecting a site - apart from the fact that it controls which maps are offered when you browse to `/dcim/sites/<sitename>/` I suppose it *might* be intended to have an upstream device from another site shown in a site-specific topology map; but this can also be done with a global topology map (one which is not associated to a site)
adam closed this issue 2025-12-29 16:28:35 +01:00
adam commented 2025-12-29 16:28:35 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (Jul 6, 2017):

Also lumping in here for good measure: I think there's a typo in the documentation:

Note that you can combine multiple regexes onto one line using semicolons.

However, the example immediately above it uses a comma, not semicolon.

access-switch\d+,oob-switch\d+
@candlerb commented on GitHub (Jul 6, 2017): Also lumping in here for good measure: I think there's a typo in the [documentation](https://netbox.readthedocs.io/en/stable/data-model/extras/#topology-maps): > Note that you can combine multiple regexes onto one line using semicolons. However, the example immediately above it uses a comma, not semicolon. ``` access-switch\d+,oob-switch\d+ ```
adam commented 2025-12-29 16:28:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 6, 2017):

When generating a topology map for a site, the devices shown are not filtered to the site selected.

This is desired behavior. This way you can associate a map with a particular site but still include devices at other sites to provide additional context e.g. for circuits.

I think there's a typo in the documentation

Yes, the example should use a semicolon. Will fix, thanks.

@jeremystretch commented on GitHub (Jul 6, 2017): > When generating a topology map for a site, the devices shown are not filtered to the site selected. This is desired behavior. This way you can associate a map with a particular site but still include devices at other sites to provide additional context e.g. for circuits. > I think there's a typo in the documentation Yes, the example should use a semicolon. Will fix, thanks.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1075
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?