So If I am not mistaken, you want to have a way of viewing log events, for a given application, along with the version right.
So right now in our carbon platform we have this[1] (this view is calling the above getPaginatedApplicationLogEvents) [image: http://2.bp.blogspot.com/--qDuRc9d5Cs/UYsfqhlbLtI/AAAAAAAABKQ/1yVzU0GDGNc/s1600/Selection_001.png] So what I am suggesting is instead of just giving application name only we given another filtering criteria to filter by the application version, as well as application name. And this can be done the same way we do store application name in the log even. Where we have another column for application version in our column family For more information on the columns we already have in the log event column family please refer[2] [1] http://2.bp.blogspot.com/--qDuRc9d5Cs/UYsfqhlbLtI/AAAAAAAABKQ/1yVzU0GDGNc/s1600/Selection_001.png [2 ] http://sparkletechthoughts.blogspot.com/2013/05/carbon-logging-framework-conversion.html Please correct me if I miss read the requirement. On Fri, Nov 1, 2013 at 8:52 PM, Harsha Thirimanna <hars...@wso2.com> wrote: > correction : war name created using application key and version. > > > *Harsha Thirimanna* > Senior Software Engineer; WSO2, Inc.; http://wso2.com > * <http://www.apache.org/>** > email: **hars...@wso2.com* <az...@wso2.com>* cell: +94 71 5186770** > twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>** > harshathirimann > linked-in: **http: <http://lk.linkedin.com/in/afkhamazeez>**// > www.linkedin.com/pub/harsha-thirimanna/10/ab8/122* > * > * > *Lean . Enterprise . Middleware* > * > * > > > On Fri, Nov 1, 2013 at 8:51 PM, Harsha Thirimanna <hars...@wso2.com>wrote: > >> Hi Amani, >> In AppFactory, we create application name using application key and >> version. In this method ("getPaginatedApplicationLogEvents") we pass >> application name . So it is concatenation of application name and version. >> So we can just give a link to download log for each and every version of >> application using this method without doing changes. We just have to think >> about whether we give this as per version or not as danushka said. >> I think better to have it gives per version. >> >> thanks >> >> >> *Harsha Thirimanna* >> Senior Software Engineer; WSO2, Inc.; http://wso2.com >> * <http://www.apache.org/>** >> email: **hars...@wso2.com* <az...@wso2.com>* cell: +94 71 5186770** >> twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>** >> harshathirimann >> linked-in: **http: <http://lk.linkedin.com/in/afkhamazeez>**// >> www.linkedin.com/pub/harsha-thirimanna/10/ab8/122* >> * >> * >> *Lean . Enterprise . Middleware* >> * >> * >> >> >> On Fri, Nov 1, 2013 at 8:14 PM, Amani Soysa <am...@wso2.com> wrote: >> >>> What we are doing in the mt-logging frame work is, we are keeping all >>> the infomation of the log event in a Column family which includes >>> ApplicationName, tenant information, priority, logger ect. If you want to >>> do version wise filtering its just a matter of adding another column and >>> setting it like how we set the application name. >>> >>> >>> And also I noticed, currently appfactory is downloading application logs >>> by calling this method "getPaginatedApplicationLogEvents" [1], it will only >>> return first 15 log events (as the page number is always 0) I think, this >>> also should get fixed. >>> >>> [1] - >>> https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/logging/org.wso2.carbon.logging.service/src/main/java/org/wso2/carbon/logging/service/LogViewer.java >>> >>> >>> >>> >>> On Fri, Nov 1, 2013 at 4:41 PM, Supun Malinga <sup...@wso2.com> wrote: >>> >>>> Hi, >>>> >>>> Great.. So is it possible to add the improvements for separate app logs >>>> in to AS itself (i.e: into platform level)?. If you can point me to the >>>> code I can have a look. >>>> For the version scenario I think each version should have a different >>>> log. It doesn't make sense if we have the logs of all versions in same log >>>> file.. >>>> >>>> thanks, >>>> >>>> >>>> On Fri, Nov 1, 2013 at 3:56 PM, Danushka Fernando >>>> <danush...@wso2.com>wrote: >>>> >>>>> Hi Supun >>>>> We have implemented that. Thing is sees separation of application is >>>>> not enough in AF side. How ever we added a new operation to logviewer >>>>> service to download logs per application in the perspective of AS. But >>>>> when >>>>> comes to AF side an application in AS seems a version of application in >>>>> AF. >>>>> So we needs to rethink what we should give users as logs. Should we >>>>> separate logs application vise only or should we go one step deeper and do >>>>> a version level log separation. And amilam was proposing a valid >>>>> improvement to the AF logging feature. >>>>> >>>>> Thanks & Regards >>>>> Danushka Fernando >>>>> Software Engineer >>>>> WSO2 inc. http://wso2.com/ >>>>> Mobile : +94716332729 >>>>> >>>>> >>>>> On Fri, Nov 1, 2013 at 2:25 PM, Supun Malinga <sup...@wso2.com> wrote: >>>>> >>>>>> Each application of a tenant.. In fact this is something we have >>>>>> already thought of from AS side. I'll send a separate note since this is >>>>>> dragging off the topic :) >>>>>> >>>>>> thanks, >>>>>> >>>>>> >>>>>> On Fri, Nov 1, 2013 at 2:21 PM, Ramith Jayasinghe <ram...@wso2.com>wrote: >>>>>> >>>>>>> Hi Supun, >>>>>>> you meant to say for each tenant ? >>>>>>> >>>>>>> >>>>>>> On Fri, Nov 1, 2013 at 2:17 PM, Supun Malinga <sup...@wso2.com>wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> For application logs also we need to come up with a proper >>>>>>>> solution. For eg:users in cloud should be able have their own log file >>>>>>>> ideally. This is very helpful in terms of AF and SaaS perspective. >>>>>>>> >>>>>>>> thanks, >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Nov 1, 2013 at 11:31 AM, Harsha Thirimanna < >>>>>>>> hars...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> As amila said, we can put a small console (default collapse and >>>>>>>>> not functioning) with each application version. If user expand the >>>>>>>>> console >>>>>>>>> , then we can run a loop to the relevant deployed server directly from >>>>>>>>> javascript without going through appfactory to view log stream like in >>>>>>>>> jenkins log viewer. >>>>>>>>> Log download option also should be there i think. >>>>>>>>> >>>>>>>>> >>>>>>>>> thanks >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> *Harsha Thirimanna* >>>>>>>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>>>>>>>> * <http://www.apache.org/>** >>>>>>>>> email: **hars...@wso2.com* <az...@wso2.com>* cell: +94 71 5186770* >>>>>>>>> * >>>>>>>>> twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>** >>>>>>>>> harshathirimann >>>>>>>>> linked-in: **http: <http://lk.linkedin.com/in/afkhamazeez>**// >>>>>>>>> www.linkedin.com/pub/harsha-thirimanna/10/ab8/122* >>>>>>>>> * >>>>>>>>> * >>>>>>>>> *Lean . Enterprise . Middleware* >>>>>>>>> * >>>>>>>>> * >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Oct 31, 2013 at 10:30 PM, Harsha Thirimanna < >>>>>>>>> hars...@wso2.com> wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> Yes it is important to have separate log file per version. >>>>>>>>>> As amila said, when we do the build and deployment ,it is better >>>>>>>>>> to have a console to view the relevant log when user hit on a button. >>>>>>>>>> >>>>>>>>>> thanks. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *Harsha Thirimanna* >>>>>>>>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>>>>>>>>> * <http://www.apache.org/>** >>>>>>>>>> email: **hars...@wso2.com* <az...@wso2.com>* cell: +94 71 5186770 >>>>>>>>>> ** >>>>>>>>>> twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>* >>>>>>>>>> *harshathirimann >>>>>>>>>> linked-in: **http: <http://lk.linkedin.com/in/afkhamazeez>**// >>>>>>>>>> www.linkedin.com/pub/harsha-thirimanna/10/ab8/122* >>>>>>>>>> * >>>>>>>>>> * >>>>>>>>>> *Lean . Enterprise . Middleware* >>>>>>>>>> * >>>>>>>>>> * >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Thu, Oct 31, 2013 at 10:03 PM, Danushka Fernando < >>>>>>>>>> danush...@wso2.com> wrote: >>>>>>>>>> >>>>>>>>>>> Another thing about logs is don't we need separate logs for each >>>>>>>>>>> version. >>>>>>>>>>> >>>>>>>>>>> Thanks & Regards >>>>>>>>>>> Danushka Fernando >>>>>>>>>>> Software Engineer >>>>>>>>>>> WSO2 inc. http://wso2.com/ >>>>>>>>>>> Mobile : +94716332729 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Thu, Oct 31, 2013 at 6:45 PM, Ramith Jayasinghe < >>>>>>>>>>> ram...@wso2.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> This can be similar to how Jenkins display build logs. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Oct 31, 2013 at 6:25 PM, Amila Maha Arachchi < >>>>>>>>>>>> ami...@wso2.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi all, >>>>>>>>>>>>> >>>>>>>>>>>>> This is not the correct time to discuss this topic since many >>>>>>>>>>>>> of you are in the WSO2Con and might miss the mail. But I thought >>>>>>>>>>>>> of >>>>>>>>>>>>> bringing this up before I forget this. >>>>>>>>>>>>> >>>>>>>>>>>>> At the moment, AF has a log viewing feature. What it does is, >>>>>>>>>>>>> talk to AS, get the logs via the LogViewer service and present it >>>>>>>>>>>>> as a >>>>>>>>>>>>> downloadable file. This is same for archived logs and real-time >>>>>>>>>>>>> logs. But >>>>>>>>>>>>> it is a pain to download a file to view the real-time logs. >>>>>>>>>>>>> Ideally what >>>>>>>>>>>>> should happen is, get the real-time logs periodically and display >>>>>>>>>>>>> them in >>>>>>>>>>>>> the a console kind of a thing. When new logs are available, we >>>>>>>>>>>>> can push the >>>>>>>>>>>>> exisitng ones down and display the new logs. With this way, we >>>>>>>>>>>>> can improve >>>>>>>>>>>>> the user experience to a great extent. >>>>>>>>>>>>> >>>>>>>>>>>>> Regards, >>>>>>>>>>>>> AmilaM. >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> *Amila Maharachchi* >>>>>>>>>>>>> Senior Technical Lead >>>>>>>>>>>>> WSO2, Inc.; http://wso2.com >>>>>>>>>>>>> >>>>>>>>>>>>> Blog: http://maharachchi.blogspot.com >>>>>>>>>>>>> Mobile: +94719371446 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Ramith Jayasinghe >>>>>>>>>>>> Technical Lead >>>>>>>>>>>> WSO2 Inc., http://wso2.com >>>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>>> >>>>>>>>>>>> E: ram...@wso2.com >>>>>>>>>>>> P: +94 776715671 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>> Architecture@wso2.org >>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Architecture mailing list >>>>>>>>>>> Architecture@wso2.org >>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Architecture mailing list >>>>>>>>> Architecture@wso2.org >>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Supun Malinga, >>>>>>>> >>>>>>>> Senior Software Engineer, >>>>>>>> WSO2 Inc. >>>>>>>> http://wso2.com >>>>>>>> email: sup...@wso2.com <sup...@wso2.com> >>>>>>>> mobile: +94 (0)71 56 91 321 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Architecture mailing list >>>>>>>> Architecture@wso2.org >>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Ramith Jayasinghe >>>>>>> Technical Lead >>>>>>> WSO2 Inc., http://wso2.com >>>>>>> lean.enterprise.middleware >>>>>>> >>>>>>> E: ram...@wso2.com >>>>>>> P: +94 776715671 >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Architecture mailing list >>>>>>> Architecture@wso2.org >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Supun Malinga, >>>>>> >>>>>> Senior Software Engineer, >>>>>> WSO2 Inc. >>>>>> http://wso2.com >>>>>> email: sup...@wso2.com <sup...@wso2.com> >>>>>> mobile: +94 (0)71 56 91 321 >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> Architecture@wso2.org >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> Architecture@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Supun Malinga, >>>> >>>> Senior Software Engineer, >>>> WSO2 Inc. >>>> http://wso2.com >>>> email: sup...@wso2.com <sup...@wso2.com> >>>> mobile: +94 (0)71 56 91 321 >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> Amani Soysa >>> Senior Software Engineer >>> Mobile: +94772325528 >>> WSO2, Inc. | http://wso2.com/ >>> >>> Lean . Enterprise . Middleware >>> >>> _______________________________________________ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Amani Soysa Senior Software Engineer Mobile: +94772325528 WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
