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.