Some comments inline. On Fri, Oct 7, 2011 at 7:52 PM, Amila Suriarachchi <am...@wso2.com> wrote:
> Here are some things I saw after doing some samples with BAM 1.3.0. I have > given here my view on that. Please comment > if I have mis configured any thing. > > 1. When I created a monitored server (with https://127.0.0.1:9445) with > message type of data BAM automatically creates another monitored sever ( > https://10.100.3.118:9445 ) with service type of data. > This should not happen. Sounds like a bug. > 2. In BAM it is possible to create monitored servers with same ip and port > with different type of data. But when selecting the servers in the dash > board it only display the ip + port. So users need to remember order it > appears the servers. Better to add the type of data or let users to define a > server name. > Agreed. > 3. BAM collects statistics data from the system statistics module. This > gives an accumulative value from the time server starts up. So if the server > restarts Service Analytics shows wrong values. Even the server does not > restarts min and max values can be wrong. > We too have understood this problem and we have identified that being independent than cumulative is the correct way to go about this. > 4. BAM activity publishing is configured globally. But I think it make more > sense to allow it at service level through service dashboard. It let users > to define xpath values to take data. These xpath values are always service > dependant. And also users may need to enable message logging only for some > services. > This seems to be a great idea. We should incorporate this at a service level. > 5. An activity service published message (with some xpath values) looks > through the dashboard looks like this. > Do we need xpath at all. If we dump the message. We just need to be able to xpath the message at the BAM side, and probably have the ability to save this search. > <message> > <s:Body xmlns:s="http://www.w3.org/2003/05/soap-envelope";> > <p:greet xmlns:p="http://www.wso2.org/types";> > <#comment /> > <name> > amila > </name> > </p:greet> > </s:Body> > </message> > > But it would be clear to have it like this seperating the name value pairs > and the soap message. > <message> > <s:Body xmlns:s="http://www.w3.org/2003/05/soap-envelope";> > <p:greet xmlns:p="http://www.wso2.org/types";> > <#comment /> > </p:greet> > </s:Body> > <name> > amila > </name> > </message> > > thanks, > Amila. > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Regards, Tharindu blog: http://mackiemathew.com/
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
