[
https://issues.apache.org/jira/browse/DISPATCH-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14967947#comment-14967947
]
Chuck Rolke commented on DISPATCH-185:
--------------------------------------
I think it would be useful to have the working group draft and your comments as
two separate documents. There is a likely dividing line between two sections
but given all the TO-DO remarks in the working group draft one can't be sure.
Having two docs fixes that.
DoS
I'm not so sure that the denial of service works out OK in Qpid C++ broker.
Customers are resigned to the fact that there's nothing they can do about it so
they live with it. Live changes to log settings in the broker were an addition
to help adjust for a log statement that unexpectedly starts logging huge
volumes. Dispatch requires all the controls you outline in the first paragraph
here especially restricting access to $management.
Custom Alerts
In steps 1..4 it sounds like you are describing behaviors of "client" and
"client library"? Maybe this is a first-draft clarity issue.
In the pattern you are describing the client probably wants notification when
the Q.size > X and another notification when Q.size < Y, where Y < X. (Bang
bang limit detection) Trying to do this all client-side is hard. Having a
'threshold alert event' with a little state really solves the problem for the
client: one event when the resource is in trouble and one event when normalcy
is restored.
Justifications
Good.
Standard event types
Good
Counting and skipping
Call them 'every-N-events alert' and 'one-shot alert'. These can be added at
any time and, yes, they are a good idea.
> Support for management notifications, log messages as notifications
> -------------------------------------------------------------------
>
> Key: DISPATCH-185
> URL: https://issues.apache.org/jira/browse/DISPATCH-185
> Project: Qpid Dispatch
> Issue Type: New Feature
> Components: Management Agent
> Affects Versions: 0.5
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: 0.6
>
> Attachments: management-events.rst
>
>
> Implement management notifications along the lines of discussion by the AMQP
> management working group (draft attached)
> As a first test, allow a management client to subscribe for logging events.
> Each client subscription should be able to set its own configuration for the
> logging modules and levels that it wishes to receive, independently of the
> global logging configuration.
> The subscription mechanism should be general (as described in attached draft)
> rather than specific to logging. Other notification event types will be added
> in future.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
