log filter

LogFilter com.eh.salestoolapi.integration.amt.controller.maintenance.filter.LogFilter setting 1:warn,2:high,3:critical
<filter-mapping>
	<filter-name>LogFilter</filter-name>
	<url-pattern>/*</url-pattern>
</filter-mapping>

import org.apache.commons.lang.StringUtils;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;

import javax.servlet.*;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpSession;

import java.io.IOException;
import java.util.Comparator;
import java.util.Iterator;
import java.util.Set;
import java.util.TreeMap;

public class LogFilter implements Filter
{
private static Log logger = LogFactory.getLog(LogFilter.class);
private TreeMap<Long, String> classification = new TreeMap<Long, String>(
new Comparator()
{
public int compare(Long obj1, Long obj2)
{
return obj2.compareTo(obj1);
}
});

@Override
public void destroy()
{
    classification.clear();
}

@Override
public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException
{
    long beforeTime = System.currentTimeMillis();

    chain.doFilter(request, response);

    long afterTime = System.currentTimeMillis();
    long takeTime = afterTime - beforeTime;
    Long minClassificationTime = classification.lastEntry().getKey();
    // if takes time(unit is ms) is less than minimum classification, directly return in view of performance
    if (takeTime < minClassificationTime)
    {
        return;
    }
    StringBuffer sb = new StringBuffer();
    Set<Long> keySet = classification.keySet();
    Iterator<Long> iter = keySet.iterator();
    while (iter.hasNext())
    {
        Long key = iter.next();
        if (takeTime >= key)
        {
            sb.append(classification.get(key));
            break;
        }
    }
    StringBuffer url = ((HttpServletRequest)request).getRequestURL();
    if (StringUtils.isNotBlank(sb.toString()))
    {
        HttpSession session = ((HttpServletRequest)request).getSession();
        String id = session.getId();

        if( StringUtils.isNotEmpty(id))
        {
            logger.warn("[LongRunningRequest:SessionId ="+session.getId()+" "+ sb + "] [Length:" + takeTime + "ms] URL: " + url);
        }else
        {
            logger.warn("[LongRunningRequest:no session" + sb + "] [Length:" + takeTime + "ms] URL: " + url);
        }

    }
}

@Override
public void init(FilterConfig filterConfig) throws ServletException
{
    String setting = null;
    try
    {
        setting = filterConfig.getInitParameter("setting");
        String[] loggingRules = setting.split(",");
        for (String rule : loggingRules)
        {
            String[] classificationArray = rule.split(":");
            // such as 4000(ms): warn
            classification.put(Long.valueOf(classificationArray[0]), classificationArray[1]);
        }
    } catch (Exception e)
    {
        logger.error("The setting '" + setting + "' of LogFilter is not correct in SalesToolAPI/web.xml" + e);
    }
}

}

### 使用 CANoe LOG Filter 进行日志过滤和处理 #### 日志过滤器概述 LOG Filter主要用于信息过滤,能够帮助用户分离出相关的信息并过滤掉无关的数据。这种功能对于分析复杂网络通信尤其有用,可以显著提高工作效率[^2]。 #### 设置通道一致性 为了确保过滤的有效性,所选的Channel应当与日志文件(例如`*.blf`)中的Network Channel相匹配。如果不确定当前使用的CAN通道,可以在“Simulation Setup”界面下的“Channels”选项卡中查看配置详情[^5]。 #### 应用分析过滤器 在Trace窗口工具栏点击相应的图标可开启分析过滤器视图。在此模式下,用户能通过将不需要关注的消息拖放到阻止过滤器(Stop Filter),而把感兴趣的内容放入通过过滤器(Pass Filter)[^4]。 ```python # Python伪代码展示如何逻辑化实现上述操作流程 def apply_log_filter(log_file, channel="CAN1"): # 打开指定的日志文件 with open(log_file, 'r') as file: data = file.read() filtered_data = [] for message in parse_messages(data): # 假设有一个函数parse_messages来解析消息 if message.channel == channel and not is_ignored(message): filtered_data.append(message) return save_filtered_results(filtered_data) def is_ignored(message): # 判断是否应该忽略该条目 pass def save_filtered_results(results): # 将筛选后的结果保存至新文件或其他存储方式 pass ``` #### 验证过滤效果 完成以上设置之后,在“Trace”界面上只会显示经过滤后的报文;同样地,在导出或保存下来的日志文件里也只保留了符合条件的数据记录[^3]。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值