Bug 1334992

Summary:	[RFE] Satellite should show in UI when required subsystems are down and resources are low
Product:	Red Hat Satellite	Reporter:	Mike McCune <mmccune>
Component:	Infrastructure	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.5.0	CC:	adprice, bkearney, cwelton, egolov, mmccune, mvanderw, ofalk, riehecky
Target Milestone:	Unspecified	Keywords:	FutureFeature, PrioBumpGSS, Reopened, UserExperience
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-02 17:53:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mike McCune 2016-05-11 05:36:47 UTC

Currently if Pulp or Candlepin are shut down there is no way upon logging into the UI to know that these required services are not functioning properly.

We need to have a banner, notification or error shown in a very obvious way that the 2 services required for operation are not functioning.

Comment 1 Evgeni Golov 2016-05-11 07:16:35 UTC

Same for MongoDB, but if that fails you will probably also see Pulp failing.

Comment 4 Mike McCune 2016-08-04 20:53:27 UTC

We are going to close out https://bugzilla.redhat.com/show_bug.cgi?id=1212555 as a dupe of this bug and expand the scope a bit to include some basic monitoring of resources required for Satellite 6 to function.

Comment 5 Adam Price 2016-08-04 20:53:38 UTC

*** Bug 1212555 has been marked as a duplicate of this bug. ***

Comment 8 Mike McCune 2016-08-08 21:53:58 UTC

This bug needs to not only cover subsystem availability but also monitor for critical levels of the following resources on the Satellite itself:

 * Disk Space
 * RAM Usage

CPU usage is not necessarily something we need to warn against as that can be a complex metric to determine when it is in a critical state.

Comment 9 Xixi 2016-08-08 23:08:06 UTC

and Case 01386027 from Bug 1207976 [RFE] Report Database Space on Satellite 6

Comment 11 Bryan Kearney 2018-09-04 18:56:27 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Comment 12 Bryan Kearney 2018-09-04 19:06:59 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Comment 13 Oliver Falk 2019-05-10 10:13:32 UTC

Hi!

I'm reopening this RHBZ against RHSAT 6.5, since I was just about to enter a similar request.

I've personally encountered it in the past with my test RHSAT instances, but also seen cases where some kind of low level monitoring would have probably prevented that a customer runs into an issue and opens some case afterwards.

I'm not talking about a full-blown monitoring solution for all systems available in RHSAT. That's something that needs to be implemented depending on the customer needs and therefore is completely out of scope here.

What I'd like to see in RHSAT is the following:
* Are all processes up and running?
* Can all Capsules be reached?
* Do we have enough disk space available for PostgreSQL?
* "                                          Squid? (A problem I really keep running into)
* Memory usage OK?
* CPU load (eventually)?

Especially the disk space monitoring for the DB and Squid would have some huge impact on cases. If the DB runs into issues, because it cannot write any more, this can easily lead to an inconstant DB. If Squid cannot write in the file system any longer, this leads to pretty strange error messages, while (eg) provisioning a new machine.

All that said, please reconsider having some basic monitoring in RHSAT UI for RHSAT.

Oliver

Related RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1215551 (pretty old already)

Comment 14 Bryan Kearney 2019-07-02 17:53:33 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.