You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2015/06/07 18:26:00 UTC
[jira] [Commented] (TS-2244) remove legacy
proxy.config.log.search_log_enabled feature
[ https://issues.apache.org/jira/browse/TS-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576328#comment-14576328 ]
Leif Hedstrom commented on TS-2244:
-----------------------------------
There's actually a whole slew of obsolete (unsupported) features here. It seems at some point, we had a "search server", which allowed you to query / search these logs. None of that code is here now, so removing all these configs / options seems like the right thing to do. There are better systems, both open source and commercial, for log searching.
> remove legacy proxy.config.log.search_log_enabled feature
> ---------------------------------------------------------
>
> Key: TS-2244
> URL: https://issues.apache.org/jira/browse/TS-2244
> Project: Traffic Server
> Issue Type: Bug
> Components: Cleanup, Logging
> Reporter: James Peach
> Assignee: Leif Hedstrom
> Labels: compatibility
> Fix For: 6.0.0
>
>
> While analyzing logging code, I came across the {{proxy.config.log.search_log_enabled}} setting. This enabled a hard-coded XML custom log format that may have been used to drive an Inktomi appliance feature.
> This has never been documented and is not generally useful to modern Traffic Server deployments. We should remove it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)