on the collation: I don’t get that many critical bugs on collation: project = TS AND component = Logging AND resolution = Unresolved AND text ~ "collation" ORDER BY due ASC, priority DESC, created ASC so, what is the problem we would like to remove it completely?
the current ATS logging a ugly but very good in performance thinking log system, the SAC is a dedicated commercial server to offer log collation service, due to that we are now open sourced, that is a good idea removing the duplicated SAC codes. In our using with syslog-ng, it’s performance may affect very busy ATS systems, that is why Yunkai pushed many collation improvements. yes, logging has some ugly bugs, but collation should not that bad after Yunkai’s work, and it does not bother you if you just logging to local disk and collection with the other systems, right? please consider keep this feature, I am very happy that a simple collation works for me out of box. sure you may find someone will take interest in supporting it, only if it is still there. thanks > 在 2015年4月21日，下午10:06，Leif Hedstrom <zw...@apache.org> 写道： > > We have a feature to do remote logging, called “log collation”. This runs > either as part of traffic_server itself, or using the stand-alone collector, > traffic_sac. The issues with log collation are > > * Not well supported, no development / fixes are done on critical bugs > * It has some severe shortcomings, such as orphaned logs never being > collected > * We feel that there are better out-of-band transports for logging, and > we shouldn’t be in this business > > Some options for collecting logs include > > * syslog-ng > * Apache Flume > * Splunk (commercial) > * etc. > > > The Jira for this is > > https://issues.apache.org/jira/browse/TS-3168 > > Unless we hear otherwise within 1 week, this feature will be removed for > 6.0.0. If there’s concerns about upgrades from 5.x to 6.0, please voice your > concerns asap. We could consider making this a deprecation in 6.0, and > removal for 7.0, but only if people really need this feature during an > upgrade period. v6.0.0 is schedule for release in ~july time frame. > > — Leif > - Yongming Zhao 赵永明
