Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve the 'Failed to create source' error message to include some hints as to what failed #33800

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

erulabs
Copy link

@erulabs erulabs commented Feb 6, 2025

What does this PR do?

Improves the 'Failed to create source' error message to include some hints as to what failed

Motivation

Screenshot 2025-02-06 at 11 14 49 AM
This is very difficult to debug in large cluster! Something is failing too parse, but I do not know what!

Describe how you validated your changes

It's valid go! I have not run local tests, still getting up to speed on this codebase

Possible Drawbacks / Trade-offs

Perhaps theres a better / more standard way of annotating the Error log?

@soberpeach
Copy link
Contributor

Hi! This is a known issue, I've merged a PR that fixes this issue for the next release here: #32976.

@erulabs
Copy link
Author

erulabs commented Feb 6, 2025

Heya @soberpeach - thank you (again!). I was about to rebase this on your changes, perhaps we could improve the failed to create source message further with ddLog.Errorf("Failed to create source for %q (provider: '%s', serviceID: '%s', source: '%s'): %v", cfg.Config.Name, cfg.Config.Provider, cfg.Config.ServiceID, cfg.Config.Source, err).

Happy to close this tho assuming you're confident about your change. Seems like these failed to parse config messages ought to be as verbose as possible since it's going to fall on the attentive sysadmin to resolve their own config in the case of failure.

@erulabs erulabs force-pushed the improve-failed-to-parse-error branch from 02801e6 to 92774a3 Compare February 6, 2025 19:28
@erulabs
Copy link
Author

erulabs commented Feb 6, 2025

I rebased the commit so if you do decide to improve that error anyways it'd be as easy as merging 👯

Thanks again!

@soberpeach
Copy link
Contributor

Thanks! I don't expect this to be much of an issue anymore, but I'll definitely come back to this if people end up hitting it in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants