简体繁体 English

仅将信息级别的日志发送到zipkin

[英]send only info level logs to zipkin

原文 2019-02-06 14:11:41 3 2 spring-boot/ spring-cloud-sleuth/ zipkin

In the micro-services based architecture , I have a services which helps me to fetch order details . 在基于微服务的体系结构中，我有一个服务可以帮助我获取订单详细信息。

Internally order details fetches - customer details , delivery details , product details . 内部订单详细信息获取-客户详细信息，交货详细信息，产品详细信息。 We have all services developed and the architecture is established. 我们已经开发了所有服务并建立了体系结构。

No we export everything to zipkin with the sampler rate of 100%. 不，我们以100％的采样率将所有内容导出到zipkin。 So it includes - INFO level logs and error level logs also , currently it is useful but we already have separate mechanism for ERROR level logs. 因此，它还包括-INFO级别日志和错误级别日志，目前它很有用，但我们已经为ERROR级别日志提供了单独的机制。

so , i just want to skip the zipkin logging for ERROR level log and send only INFO level logs to zipkin 因此，我只想跳过zipkin日志记录错误级别日志，而仅将INFO级别日志发送到zipkin

I tried searching through, but could not get any help, i am newbie to micro services 我尝试搜索，但无法获得任何帮助，我是微服务的新手

any help is appreciated , thank you 任何帮助表示赞赏，谢谢

2 个解决方案

Zipkin is a solution for distributed tracing. Zipkin是用于分布式跟踪的解决方案。 Specifically it allows to track latency problems in distributed system. 具体来说，它允许跟踪分布式系统中的延迟问题。 Also it's a greate tool for debugging/investigating problems in your application. 这也是调试/调查应用程序中问题的绝佳工具。 So by definition it requires to collect successful and failed traces. 因此，根据定义，它需要收集成功和失败的跟踪。 However traces have nothing to do with logging. 但是，跟踪与日志记录无关。

Assuming you mean controlling the logging level of Zipkin server, then you can just set it using --logging.level.zipkin2=INFO . 假设您要控制Zipkin服务器的日志记录级别，则可以使用--logging.level.zipkin2 = INFO进行设置。

I don't understand the problem. 我不明白这个问题。 You don't send logs to Zipkin. 您不会将日志发送到Zipkin。 You send spans to Zipkin. 您将跨度发送到Zipkin。 Zipkin has nothing to do with logs. Zipkin与日志无关。