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

Convert Script log JSON to DB records #9323

New Issue
Open
opened 2025-12-29 20:48:26 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:48:26 +01:00
Owner
Copy Link

Originally created by @arthanson on GitHub (Mar 5, 2024).

NetBox version

v4.0.0

Feature type

Change to existing functionality

Proposed functionality

Currently Script log records are stored as a JSON blob on the Job object, this proposal is to create a ScriptLog Model and use that for storing log records.

Use case

As requested in #10587 There are requests to add filtering and export functionality to Script logs, this would especially be helpful when there are lots of test or log records. This is currently not feasible when they are stored as JSON as the NB code relies on there being querysets to the objects.

Database changes

Create a new ScriptLog object

External dependencies

None

Originally created by @arthanson on GitHub (Mar 5, 2024). ### NetBox version v4.0.0 ### Feature type Change to existing functionality ### Proposed functionality Currently Script log records are stored as a JSON blob on the Job object, this proposal is to create a ScriptLog Model and use that for storing log records. ### Use case As requested in #10587 There are requests to add filtering and export functionality to Script logs, this would especially be helpful when there are lots of test or log records. This is currently not feasible when they are stored as JSON as the NB code relies on there being querysets to the objects. ### Database changes Create a new ScriptLog object ### External dependencies None
adam added the type: featurenetboxstatus: backlogcomplexity: high labels 2025-12-29 20:48:26 +01:00
adam commented 2025-12-29 20:48:27 +01:00
Author
Owner
Copy Link

@alehaa commented on GitHub (Mar 8, 2024):

Maybe this could be used to return log records while the script is running, too. Then users would get some response about the progress of a long running script.

@alehaa commented on GitHub (Mar 8, 2024): Maybe this could be used to return log records while the script is running, too. Then users would get some response about the progress of a long running script.
adam commented 2025-12-29 20:48:28 +01:00
Author
Owner
Copy Link

@alehaa commented on GitHub (Jul 28, 2024):

After completion of #15692 it would be nice if we could add this as general JobLogLines to be used by both background jobs and scripts. However, a problem to be covered are transactions, so log entries won't be deleted when the script / job fails.

@alehaa commented on GitHub (Jul 28, 2024): After completion of #15692 it would be nice if we could add this as general `JobLogLines` to be used by both background jobs and scripts. However, a problem to be covered are transactions, so log entries won't be deleted when the script / job fails.
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: high netbox status: backlog 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#9323
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?