Bug 683599

Summary:	Documentation update: How to use configurable queue threshold alerts
Product:	Red Hat Enterprise MRG	Reporter:	Ted Ross <tross>
Component:	Messaging_Programming_Reference	Assignee:	Alison Young <alyoung>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Frantisek Reznicek <freznice>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.3	CC:	esammons, freznice, jneedle, sburgess
Target Milestone:	2.0
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-24 02:53:26 UTC	Type:	---
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:	660526
Bug Blocks:	660289, 660531

Description Ted Ross 2011-03-09 19:48:00 UTC

The new feature "Configurable queue threshold alerts" requires documentation in the user guide as to how to configure the thresholds and how to receive and interpret the resulting events.

Comment 1 Susan Burgess 2011-03-24 11:52:47 UTC

Alison, another one for you to qa_ack

Comment 3 Frantisek Reznicek 2011-04-19 11:07:35 UTC

The QA review:

- There is need to highlight that qpid.alert_count and x-qpid-maximum-message-count are equivalent for setting message count alert  threshold

- There is need to highlight that qpid.alert_size and x-qpid-maximum-message-size are equivalent for setting byte count alert threshold

- Similarly for qpid.alert_repeat_gap and x-qpid-minimum-alert-repeat-gap pair

- There is need to highlight that if both message count and byte count alerts are configured then single alert will be triggered for condition which occurs first

- reference to self.do_threshold_test() is useless for customers.
  I would rather refer to whole unit test, for instance:

Example of queue alerts usage can be found in:
# rpm -ql qpid-tests | grep threshold.py$
/usr/lib/python2.4/site-packages/qpid_tests/broker_0_10/threshold.py

  The other way which might be more useful for customers can be Gordon's example mentioned in bug 660289, comment 5 pont 2] - this uses just well known tools qpid-config & spout and drain.


-> ASSIGNED

Comment 4 Frantisek Reznicek 2011-04-21 09:57:45 UTC

I recommend to better specify the qpid.alert_repeat_gap / x-qpid-minimum-alert-repeat-gap functionality according bug 660289, comment 12.

Especially the fact that there is no mechanism for delaying the queue alert somewhere and retriggering automatically after qpid.alert_repeat_gap / x-qpid-minimum-alert-repeat-gap period. i.e. having queue in state which caused first initial alert is not enough for seeing the next alert (after lert_repeat_gap period) automatically - there has to be queue state change...

Comment 6 Frantisek Reznicek 2011-05-17 10:22:57 UTC

I'm fine with the feature description.

-> VERIFIED