Details
-
Type:
Story
-
Status: Done
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 3.5.0
-
Fix Version/s: 3.5.0
-
Component/s: Scheduled Tasks
-
Labels:None
-
Story Points:3
-
Release Note:Yes
-
Epic Link:
-
Sprint:Core Team - Sprint 97, Core - Sprint 98
Description
Background
There are a number of long-running tasks whose specifics we need to audit (self-repair tasks being a good example, but also purging releases, snapshots, etc.), but we don't want to a) fill the nexus log with a million line items, or b) lose information at the whim of a customer's log levels. Support frequently gets requests from users asking to understand what happened to specific artifacts.
Acceptance
- Create a service that can accept all these detailed actions, in large volumes
- One log file per run of a given scheduled task
- Output files should be dated, clearly indicate which task was run
- Emit the log file location into the log at the start and end of the scheduled task
- Include task logs in the support tools zip
Attachments
Issue Links
- is depended on by
-
NEXUS-12389 if the component database references a soft-deleted blob then prevent blob store compaction task from hard deleting the blob
-
- Done
-
- links to
- mentioned in
-
Page Loading...