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.

Sign up for GitHub

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

Jump to bottom

Improved logging and eventing #104

Closed
negz opened this issue Jan 3, 2020 · 1 comment
Closed

Improved logging and eventing #104

negz opened this issue Jan 3, 2020 · 1 comment
Assignees
@negz
Labels
enhancement New feature or request

Comments

@negz
Copy link
Member

negz commented Jan 3, 2020

What problem are you facing?

It's currently difficult for Crossplane users and operators to debug issues. Most errors are reflected only as a conditioned status, meaning only the latest error is exposed. Additionally, we have little to no logging and timeseries data. crossplane/crossplane#858 began thinking about how we might improve our logging and events.

How could Crossplane help solve your problem?

It would be good to start prototyping how we could enable this in our existing reconciler scaffolds.
@negz negz added the enhancement New feature or request label Jan 3, 2020
@negz negz self-assigned this Jan 6, 2020
This was referenced Jan 24, 2020
Closed
Closed
@negz
Copy link
Member Author

negz commented Jan 31, 2020

This was fixed by #108 - all crossplane-runtime reconcilers now emit logs and events. All infrastructure stacks have been updated to use these changes.

@negz negz closed this as completed Jan 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@negz negz

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@negz