Bug 970233

Summary:	[RFE] Need ability to create an alert definition programmatically via CLI/Remote API
Product:	[JBoss] JBoss Operations Network	Reporter:	Larry O'Leary <loleary>
Component:	CLI	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED WONTFIX	QA Contact:	Mike Foley <mfoley>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	JON 2.4.2, JON 3.0.0	CC:	bkramer, dsteigne, fbrychta, gcooper, hrupp, jshaughn, loleary, myarboro, tsegismo
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	JON 3.4.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	617202	Environment:
Last Closed:	2019-03-07 15:40:30 UTC	Type:	Enhancement
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	617202
Bug Blocks:

Description Larry O'Leary 2013-06-03 19:05:22 UTC

+++ This bug was initially created as a clone of Bug #617202 +++

Need an option to create alert via CLI

For a large-scale system it is vital to be able to automate all the steps required to set up a new node. One of such steps is creation of alerts. Currently this action has to be done manually via web UI which is not suitable.

--- Additional comment from John Mazzitelli on 2011-01-06 09:02:53 EST ---



--- Additional comment from Jay Shaughnessy on 2012-04-10 09:49:19 EDT ---


Just to be clear, this is a request to create alert definitions, not to inject
alerts. I updated the title.

--- Additional comment from Nabeel Saad on 2012-11-26 17:34:21 EST ---

What's the current planning for this bug given that it's been open since 2010?  It is a fairly important feature... and allows us to say to customers that they can do everything via the CLI that they can do through the GUI...

Comment 8 Filip Brychta 2019-03-07 15:40:30 UTC

JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.