-
Bug
-
Resolution: Not a Bug
-
Normal
-
1.0
-
None
-
2
-
False
-
-
False
-
-
-
RHDH Core Platform 3265
Description of problem:
If there is a wrong URL (typo, no permissions, etc.) in the catalog, RHDH doesn't log any errors or warnings. So users are unaware that the catalog data are not being fetched or why they don't see them in the catalog.
For example If I put something like this into my config
catalog: locations: - type: url target: https://github.com/non-existing/non-existing/blob/master/file.yaml
With upstream Backstage I see a Warning in logs
[1] 2024-10-22T14:16:31.180Z catalog warn Unable to read url, NotFoundError: Request failed for https://raw.githubusercontent.com/non-existing/non-existing/master/file.yaml, 404 Not Found entity=location:default/generated-944f8aae6e091238b453209e59efec55f84b4ca8 location=url:https://github.com/non-existing/non-existing/blob/master/file.yaml
With RHDH, I don't see any warnings or errors in the logs.
After enabling debug log, I can see it logged as a debug message.
{"level":"debug","message":"Event received: topic=experimental.catalog.errors, metadata=undefined, payload={\"entity\":\"location:default/generated-621c9d3ebcaa7aca7e06a9768db4364cdcad7e34\",\"location\":\"url:https://example.com/non-existing-file.yaml\",\"errors\":[{}]}","service":"backstage","timestamp":"2024-10-22 14:15:34"}
This is important information that should not be hidden as a debug message.
Reproducibility (Always/Intermittent/Only Once):
Always
Build Details:
RHDH 1.3.0
probably 1.2.0 as well (haven't tested it)
