On Fri, Apr 15, 2011 at 10:58 PM, Sumedha Rubasinghe <[email protected]>wrote:
> > > On Fri, Apr 15, 2011 at 10:48 PM, Senaka Fernando <[email protected]> wrote: > >> Hi all, >> >> Small question. Based on Amani's explanation, why do we have URL + Port? >> Isn't Port redundant? >> >> I believe correct terminology should be server & port. That goes well with > Log4j Syslog-ng terminology[2] as well. > /sumedha > [2] http://wiki.apache.org/logging-log4j/syslog > I felt the same, initially. But Amani's explanation confused me a bit, since the value for URL was, http://127.0.0.1/logs. That endpoint clearly has more than the host name in it. So, I'm still in doubt. Anyway in general, I'm +1 for using Host + Port instead of URL, since syslog is something that's not directly bound to HTTP or something, AFAIK (correct me if I'm wrong). Thanks, Senaka. > >> Thanks, >> Senaka. >> >> >> On Fri, Apr 15, 2011 at 10:43 PM, Sumedha Rubasinghe <[email protected]>wrote: >> >>> >>> >>> On Fri, Apr 15, 2011 at 7:45 PM, Charitha Kankanamge >>> <[email protected]>wrote: >>> >>>> Hi all, >>>> >>>> I see the following Syslog property config element in Logging management >>>> UI of the latest AS pack. What is this supposed to do? Can someone please >>>> explain or point me to the relevant discussion (or document/article)? >>> >>> >>> Charitha, >>> How this fits into an enterprise deployment is as follows. >>> >>> Syslog is a standard well known protocol where there is a syslog server & >>> clients (syslog event publishers). Most of the server software(OS, app >>> servers, email, database engines,web servers) support acting as syslog >>> clients. From a system administration PoV, it's very convenient to see all >>> the log events coming to a single server & ability to monitor everything >>> from a single console. >>> >>> Log4j by default provides the capability of publishing to syslog servers. >>> So we had this capability b4. This UI is part of enhancement related to >>> Stratos logging. >>> >>> Check [1] for additional info. >>> /sumedha >>> >>> [1] http://www.monitorware.com/common/en/articles/syslog-described.php >>> >>> >>>> [image: Screenshot-WSO2 Management Console - Mozilla Firefox.png] >>>> >>>> Regards >>>> Charitha >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> [email protected] >>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> *Senaka Fernando* >> Product Manager - WSO2 Governance Registry; >> Associate Technical Lead; WSO2, Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://www.linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2, Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://www.linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
