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

Allow configuration of the Sentry send_default_pii parameter #9939

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

Originally created by @mulmat on GitHub (Jul 3, 2024).

Originally assigned to: @mulmat on GitHub.

NetBox version

v4.0.6

Feature type

Change to existing functionality

Proposed functionality

Allow configuration of the Sentry send_default_pii parameter.

Also default to not send default pii data - to avoid sending auth tokens and session-ids.

Use case

For our use case, we do not want to log sensitive data such as auth tokens or session-ids from the cookies. By allowing configuration of the send_default_pii parameter this can be accomplished.
I would also like to change the default behavior so scrubbing these data points are the default behavior (a.k.a send_default_pii=False - just like it is in the Sentry sdk).

Database changes

No response

External dependencies

No response

Originally created by @mulmat on GitHub (Jul 3, 2024). Originally assigned to: @mulmat on GitHub. ### NetBox version v4.0.6 ### Feature type Change to existing functionality ### Proposed functionality Allow configuration of the Sentry `send_default_pii` parameter. Also default to not send default pii data - to avoid sending auth tokens and session-ids. ### Use case For our use case, we do not want to log sensitive data such as auth tokens or session-ids from the cookies. By allowing configuration of the `send_default_pii` parameter this can be accomplished. I would also like to change the default behavior so scrubbing these data points are the default behavior (a.k.a `send_default_pii=False` - just like it is in the Sentry sdk). ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:24:42 +01:00
adam closed this issue 2025-12-29 21:24:43 +01:00
adam commented 2025-12-29 21:24:43 +01:00
Author
Owner
Copy Link

@mulmat commented on GitHub (Jul 3, 2024):

PR here

@mulmat commented on GitHub (Jul 3, 2024): PR [here](https://github.com/netbox-community/netbox/pull/16803)
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 complexity: low status: accepted type: feature
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#9939
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?