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

Feature Request: Webhook On Selectable Fields #2754

New Issue
Closed
opened 2025-12-29 18:21:46 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:21:46 +01:00
Owner
Copy Link

Originally created by @jvanderaa on GitHub (Jul 22, 2019).

Environment

  • Python version: 3.6.3
  • NetBox version: 2.5.8

Proposed Functionality

Looking to select which fields that are modified to trigger a webhook instead of any device update. Extend to the custom fields selection as well.

Use Case

We are currently using a custom_field of Monitored to give a source of truth of whether or not a device is monitored. Some clients choose not to have monitoring enabled. Thus the need to monitor some and not others.

We would like to trigger a process using just standard webhook to kick off jobs when the custom field and possibly other attributes that could be selected get updated.

Database Changes

Unsure

External Dependencies

Originally created by @jvanderaa on GitHub (Jul 22, 2019). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: <!-- Example: 3.5.4 --> 3.6.3 * NetBox version: <!-- Example: 2.3.6 --> 2.5.8 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Looking to select which fields that are modified to trigger a webhook instead of any device update. Extend to the custom fields selection as well. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case We are currently using a custom_field of `Monitored` to give a source of truth of whether or not a device is monitored. Some clients choose not to have monitoring enabled. Thus the need to monitor some and not others. We would like to trigger a process using just standard webhook to kick off jobs when the custom field and possibly other attributes that could be selected get updated. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes Unsure <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies
adam closed this issue 2025-12-29 18:21:46 +01:00
adam commented 2025-12-29 18:21:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 23, 2019):

Webhooks are implemented so that one is sent in response to any change in an associated object. It is left to the receiver to decide whether they should act on the information being sent.

@jeremystretch commented on GitHub (Jul 23, 2019): Webhooks are implemented so that one is sent in response to _any_ change in an associated object. It is left to the receiver to decide whether they should act on the information being sent.
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#2754
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?