Bug 855744 – RFE: Improve user awareness of agent/server state and various error/warning conditions

Bug 855744 - RFE: Improve user awareness of agent/server state and various error/warning conditions

Summary:	RFE: Improve user awareness of agent/server state and various error/warning c...

Status:	NEW

Aliases:	None

Product:	RHQ Project
Classification:	Other
Component:	Agent, Core Server, Core UI (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified (vote)
Target Milestone:	---
Target Release:	---
Assigned To:	Lukas Krejci
QA Contact:	Mike Foley
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	743727
Blocks:	863092
	Show dependency tree / graph

Reported:	2012-09-10 03:32 EDT by Lukas Krejci
Modified:	2012-10-15 06:34 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Lukas Krejci 2012-09-10 03:32:08 EDT

Description of problem:

There are multiple areas where the user doesn't get enough info about the agent to determine the "health" of the agent or one of its subsystems.

Exposing more information like that would be beneficial to the user so that they can fine-tune the performance of various subsystems (without opening a support ticket or asking questions on our forums).

This bug is an umbrella for other BZs detailing the individual enhancements we will be making as part of this effort.

Comment 1 Lukas Krejci 2012-10-15 06:34:28 EDT

This is not strictly tied to the agent, the user should also for example have an idea about the "saturation" of the data purge jobs on the server (i.e. if the server can keep up with the inflow of measurements from the agents).

Note You need to log in before you can comment on or make changes to this bug.