kilianc/rtail

Support for third party log sources

Open

#97 创建于 2015年10月10日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)CSS (1,624 star) (111 fork)batch import
enhancementhelp wanted

描述

Providing a means for third parties to push logs to rtail-server would be useful. I would expect some configurable form of delineation to specify stream source, etc and a general form of the message to be sent.
Example from the log.io page: https://github.com/NarrativeScience/Log.io#server-tcp-interface

+log|my_stream|my_node|info|this is log message\r\n

Particularly useful when logs originate from systems that do not have unix pipes. (Windows)

贡献者指南

技术栈
nodejs
领域
backendcliapi
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
TCP/IP networkingNode.jsrtail codebase
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
The issue requests a TCP interface for third party log sources, similar to Log.io's TCP protocol. Research the Log.io server TCP interface linked in the issue (https://github.com/NarrativeScience/Log.io#server tcp interface). Explore the rtail server codebase (likely in the rtail repository under the server directory) to understand its existing architecture and message handling. Consider implementing a TCP server that accepts messages in a format like '+log|stream|node|level|message'. Ensure the server can parse this format and forward logs to connected WebSocket clients. The implementation should be configurable and well documented.