Log repository issues separately. #1054
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Koenvh1
approved these changes
Aug 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces separate logs for each repository and publication point and puts log messages for them there. By default, these messages are not sent to the process log any more. This is in response to many people getting worried about these issues that are not under their control and can be ignored.
The messages are available both via the
/statusand/api/v1/statusHTTP endpoints grouped by the repository or publication point which makes it much easier to see what has issues.The new
log-repository-issuesconfiguration option allows sending the issues to the process log as well, restoring the previous behaviour for people who prefer it.Fixes #1031.