kilianc/rtail

Support for third party log sources

Open

#97 opened on Oct 10, 2015

View on GitHub
 (1 comment) (0 reactions) (0 assignees)CSS (111 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (1,624 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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)

Contributor guide

Research direction
Investigate rtail server's current architecture and TCP handling. Examine log.io's TCP interface as a reference. Design a protocol for third party log sources, implement a TCP listener that parses messages in a similar format, and integrate with existing stream handling.
Tech stack
javascriptnodejs
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Node.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60