Catalog: Noisy logging of NotFoundErrors for optional entries
See original GitHub issueExpected Behavior
When discovering catalog entries in GitHub or GitLab, many discovered repositories may not actually contain a catalog-info.yaml
file. This is okay, because these discovered entries are marked as optional
by the discovery processors.
I would expect these missing catalog-info.yaml
files to not cause any warnings in the logs, since we expect plenty of repositories to not contain these files, and they’re optional, after all.
Current Behavior
Every optional catalog entry url that is not found throws a NotFoundError
which is logged as a warning. This results in a lot of warn
logs every refresh interval.
Possible Solution
Log NotFoundError
at a lower level (i.e. debug
) for optional entries.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:5 (2 by maintainers)
Top Results From Across the Web
backstage/CHANGELOG.md at master - GitHub
3368f27aef: Fixed the handling of optional locations so that the catalog no longer logs NotFoundError s for missing optional locations. Updated dependencies.
Read more >Optional Parameters - IBM
specifies that entries that refer to the named catalog are not scanned. Up to 99 catalog names can be coded. CATALOG can only...
Read more >Change Log for Plesk Obsidian
Log Browser now shows the list of all services that exist on the server and their statuses on the “Overview” tab. You can...
Read more >Tickets — LSST Science Pipelines
This page lists individual work tickets that went into LSST Science Pipelines releases. For a broad descriptions of these tickets, see the release...
Read more >Cisco SD-WAN Command Reference - Operational ...
(Optional) Specifies ingress interface name. Note: It is must to choose VPN to configure the interface. logging. (Optional) Enables packet ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey,
I have the same problem. The problem boils down to gitlab-discovery emitting a Location for each project no matter whether it contains a catalog-info.yml file or not.
My suggestion would be to have it test-fetch the specified file before emitting anything. I am opening a PR with that in mind.
This was fixed by https://github.com/backstage/backstage/pull/8343