-
Notifications
You must be signed in to change notification settings - Fork 451
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
Write failed manifests to log at debug level #872
Comments
The specific error above seems to arise from
with a configmap created by
|
See also #873 |
What do you mean by manifest? The CR created by user or the OTEL configmap created by the operator. Note that the OTEL configmap should match the collector config from the CR so user has access to it. |
When the reconciler fails to apply a manifest, there's very little the user can do to figure out exactly what the failed manifest payload was or where it came from.
It would be very helpful to have a debug level log record to capture the manifest payload when apply fails.
For example, this recent error I hit:
is inscrutable at best without being able to access the generated ConfigMap. The value shown is not present in the input CRD, and when decoded as hex does not appear to have any textual content.
When
--zap-log-level=debug
is passed, it'd be helpful to have the generated configmap dumped.The text was updated successfully, but these errors were encountered: