Add contacts to services #9096

New Issue

adam · 2025-12-29T20:45:23+01:00

adam commented

2025-12-29 20:45:23 +01:00

Originally created by @dmulyalin on GitHub (Jan 16, 2024).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.6.9

Feature type

New functionality

Proposed functionality

Add contacts for services definitions

Use case

As we define services they naturally managed or owned by tems, engineers or companies, it would be beneficial for Netbox user to be able to map service owners to services using contacts.

Database changes

I believe services model need to be extended with the column referencing contacts same goes for contacts.

External dependencies

No response

Originally created by @dmulyalin on GitHub (Jan 16, 2024). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.6.9 ### Feature type New functionality ### Proposed functionality Add contacts for services definitions ### Use case As we define services they naturally managed or owned by tems, engineers or companies, it would be beneficial for Netbox user to be able to map service owners to services using contacts. ### Database changes I believe services model need to be extended with the column referencing contacts same goes for contacts. ### External dependencies _No response_

adam added the status: accepted type: feature complexity: low labels 2025-12-29 20:45:23 +01:00

adam closed this issue

2025-12-29 20:45:23 +01:00

adam commented

2025-12-29 20:45:23 +01:00

@jeffgdotorg commented on GitHub (Apr 3, 2024):

Thanks for your interest in helping improve NetBox. I'm moving this issue along for engineering review, because I'm not sure whether this work can be done within an existing release train. It may need to be scheduled out for a minor release boundary.

@jeffgdotorg commented on GitHub (Apr 3, 2024): Thanks for your interest in helping improve NetBox. I'm moving this issue along for engineering review, because I'm not sure whether this work can be done within an existing release train. It may need to be scheduled out for a minor release boundary.

adam commented

2025-12-29 20:45:24 +01:00

@jeremystretch commented on GitHub (Apr 4, 2024):

As we define services they naturally managed or owned by tems, engineers or companies, it would be beneficial for Netbox user to be able to map service owners to services using contacts.

Can you cite a real-world use case? It would help to better understand how you're using services in NetBox.

@jeremystretch commented on GitHub (Apr 4, 2024): > As we define services they naturally managed or owned by tems, engineers or companies, it would be beneficial for Netbox user to be able to map service owners to services using contacts. Can you cite a real-world use case? It would help to better understand how you're using services in NetBox.

adam commented

2025-12-29 20:45:24 +01:00

@dmulyalin commented on GitHub (Apr 5, 2024):

Sure.

DHCP service hosted behind 10.1.2.3 IP address UDP port 67, DHCP service managed by DHCP Services Team, Team can be contacted via email "dhcpservices@acma.com" or phone "1234 1234 4321" and role of the team is "owner". There is also TAC team that helps to maintain DHCP records, team can be contacted using "tac-dhcprecords@acma.com email" or via phone "1234 1234 1234" and role of the team is "maintainer". Currently there is no native way to capture Teams relationship with DHCP service, having contacts linked with service could be the way to address that.

Same goes for other services such as DNS, Tacacs, Radius, Syslog, Telemetry/GNMI/SNMP Collectors - all services usually managed by a dedicated Team or have an owner that can be documented in Netbox using contacts. Real world use for this information could be to:

identify escalation points in case of service failure
perform impact analysis and produce a notification list

@dmulyalin commented on GitHub (Apr 5, 2024): Sure. DHCP service hosted behind 10.1.2.3 IP address UDP port 67, DHCP service managed by DHCP Services Team, Team can be contacted via email "dhcpservices@acma.com" or phone "1234 1234 4321" and role of the team is "owner". There is also TAC team that helps to maintain DHCP records, team can be contacted using "tac-dhcprecords@acma.com email" or via phone "1234 1234 1234" and role of the team is "maintainer". Currently there is no native way to capture Teams relationship with DHCP service, having contacts linked with service could be the way to address that. Same goes for other services such as DNS, Tacacs, Radius, Syslog, Telemetry/GNMI/SNMP Collectors - all services usually managed by a dedicated Team or have an owner that can be documented in Netbox using contacts. Real world use for this information could be to: - identify escalation points in case of service failure - perform impact analysis and produce a notification list

Sign in to join this conversation.

Branches Tags

main

21050-device-oob-ip-may-become-orphaned

21102-fix-graphiql-explorer

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#9096