Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: neutral (athena.apache.org: 216.139.236.26 is neither permitted
 nor denied by domain of michal.warecki@gmail.com)
Date: Tue, 21 Feb 2012 06:49:31 -0800 (PST)
From: "michal.warecki" <michal.warecki@gmail.com>
To: dev@camel.apache.org
Message-ID: <1329835771926-5502403.post@n5.nabble.com>
In-Reply-To: <4F4352D2.7000603@gmail.com>
References: <1329672873388-5497221.post@n5.nabble.com>
 <4F4137AC.9080009@die-schneider.net>
 <1329727384860-5498485.post@n5.nabble.com>
 <4F4273BD.5050301@die-schneider.net>
 <5455F7F0-21E3-4760-9CFE-E4353AD7E089@code-house.org>
 <4F4352D2.7000603@gmail.com>
Subject: Re: [DISCUSS] Camel Alerts
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Camel management support for runtime information build on the top of JMX is
interesting idea.
We could add some notification broadcasters and MBean's. "Alert" will
analyze informations from notifications and if needed (based on
configuration) send to SMNP or SMTP.

SMNP should be preconfigured with: IOD, address, version, username,
password, passphrase.
For SMTP: server, port, username, password.

How do you think, what are the pros and cons of such a solution to support
JMX?

--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Camel-Alerts-tp5497221p5502403.html
Sent from the Camel Development mailing list archive at Nabble.com.