Refactor filter view to be more tightly intergrated with Netbox and improve capabilities

[sol1-matt]

This issue is a placeholder for list of potential improvements to filter view

This refactor has a number of goals

• Use native django calls to get data instead of the api
• Return data to the default Netbox Bulk View tables instead of datatables
• Improve the query language so it is possible to apply unique filters per object type
• Improve the query language so it is possible to do thing Netbox can't currently do through the api, things like
  • date periods relative to now eg: everything in the last 180days
  • available ports
  • support linked item lookup, eg: return the site.address when looking up a device even though device can't see site.address directly
• Allow both url based GET requests and json payload based POST requests
• Allow links destinations to be defined, eg: primary_ip.address:primary_ip.address__regex[^/]+ vs primary_ip.address:primary_ip.id

[sol1-matt]

possible url format and json payload

filters=dcim.device:role=firewall;tenant=tenant-viacom|virtualization.virtualmachine:status=active;site=sydney;tenant=tenant-viacom&columns=name,status,site.name,device_type.model,primary_ip.address,custom_fields.FriendlyName,comments&group_by=tenant.name

filters=<scope>:<key>=<value>[;<key>=<value>] |

columns=<field1>,<field2>,<field3>,

group_by=<field>

same data as a json payload

{
  "filters": {
    "dcim.device": {
      "tenant": "tenant-viacom"
      "role": "firewall"
    },
    "virtualization.virtualmachine": {
      "tenant": "tenant-viacom"
      "status": "active",
      "site": "sydney"
    }
  },
  "columns": [
    "name",
    "status",
    "site.name",
    "device_type.model",
    "primary_ip.address",
    "custom_fields.FriendlyName",
    "comments"
  ],
  "group_by": "tenant.name"
}

advanced filtering based on Django’s ORM and REST framework

Suffix	Meaning	Example
exact	Exact match (default, usually implicit)	status=active
iexact	Case-insensitive exact match	name__iexact=device01
contains	Substring match	name__contains=router
icontains	Case-insensitive substring match	name__icontains=router
in	Matches one of a list of values	status__in=active,offline
gt	Greater than	created__gt=2024-12-31
gte	Greater than or equal to	created__gte=2025-01-01
lt	Less than	created__lt=2025-07-01
lte	Less than or equal to	created__lte=2025-07-01
startswith	Starts with	name__startswith=sw
istartswith	Case-insensitive starts with	name__istartswith=sw
endswith	Ends with	name__endswith=01
iendswith	Case-insensitive ends with	name__iendswith=01
isnull	Field is null or not	serial__isnull=true
regex	Regex match	name__regex=^sw\d+$
iregex	Case-insensitive regex match	name__iregex=^sw\d+$

todo: linked object filtering, eg: all devices that have a ip in range or all switches that have free ports

[sol1-matt]

filter=dcim.interface:(mtu__gt=1400&mtu__lt=1500)|mtu=1800

filter with a grouped and ((&)) and a or (|)
expected to return a interface with mtu's between 1400 and 1500 or 1800

[sol1-matt]

filter=dcim.device:(tenant=tenant-viacom&role=firewall&related.dcim.interface:dcim.device.id=id&((mtu__gt=1400&mtu__lt=1500|mtu=1800)))

same as above but related tells us we want to join the data together using a relationship, we also define that relationship

not sure how we manage depth and width
eg: device -> site, tenant vs device -> interface -> ip address -> vlan