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

Provide a way to flag DataSource beans as essential or non-essential for the dbHealthIndicator #6807

Closed
philwebb opened this issue Sep 1, 2016 · 1 comment
Closed

Provide a way to flag DataSource beans as essential or non-essential for the dbHealthIndicator #6807

philwebb opened this issue Sep 1, 2016 · 1 comment
Labels
status: superseded An issue that has been superseded by another type: enhancement A general enhancement

Comments

@philwebb
Copy link
Member

philwebb commented Sep 1, 2016

If the dbHealthIndicator is being used to show results from multiple datasources, it's possible that some may be critical to operation, where as others don't actually prevent a service from running if they are down. It would be nice if the aggregate dbHealthIndicator could have more smarts about knowing when a DataSource is really critical or not.
@philwebb philwebb added the type: enhancement A general enhancement label Sep 1, 2016
@philwebb philwebb modified the milestone: 1.5.0 Sep 1, 2016
@wilkinsona
Copy link
Member

Superseded by #14022.

@wilkinsona wilkinsona added the status: superseded An issue that has been superseded by another label Jan 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: superseded An issue that has been superseded by another type: enhancement A general enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@philwebb @wilkinsona