[jira] [Commented] (TS-2244) remove legacy proxy.config.log.search_log_enabled feature

["Zhao Yongming (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842138#comment-13842138 ] 

Zhao Yongming commented on TS-2244:
-----------------------------------

that search log use case is when you have some problem in your system, and would like to filter out some of the suspecting requests to a seperated log file for investing, and do not need to go through all the logs which may not even logged or not logged locally.

for example, you have a very busy site and you want to catch a not so frequent query, in the log.

call it useful or not, depends on the logging system you relay on, the origin ATS design is you can do it here :D

> 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
>             Fix For: 4.2.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.1#6144)