[#RHQ-342] fire alerts on externally modified configs (i.e. configs not modified via RHQ)

RHQ Project

fire alerts on externally modified configs (i.e. configs not modified via RHQ)

Created: 21/Apr/08 08:56 AM Updated: 30/Jan/09 01:24 PM

Component/s:

FX - Configuration

Fix Version/s:

1.2

Time Tracking:

Not Specified

Resolution Date:	19/Oct/08 03:44 PM
Date of First Response:	07/Jul/08 11:13 AM
Tester:	Corey Welton
VCS Revision:	1,806

Description

« Hide

Then companies could have a corporate policy that RHQ should be used for all config modifications and be alerted by RHQ itself if this policy is violated.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Joseph Marques - 07/Jul/08 11:13 AM

this is a non-trivial amount of functionality to implement in 1.1 - furthermore, 1.2 is all about enhancing various server-side pieces of functionality. so moving this to 1.2 time frame.

[ Permlink | « Hide ]

Joseph Marques - 19/Oct/08 03:44 PM

rev1806 - add the ability to alert on changes to the resource configuration;
UI will suppress option to alert on changes if the resourceType does not support that facet;
added monitoring to Alerts Engine mbean - cache element count, matches (per minute), and processing time (per minute);

[ Permlink | « Hide ]

Jeff Weiss - 30/Jan/09 01:24 PM

Between corey and I, I think we've hit this pretty thoroughly.

jira.rhq-project.org has been archived and is now in read-only mode.

fire alerts on externally modified configs (i.e. configs not modified via RHQ)