Consider a unix domain socket for log forwarding

Open
#49 11 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
c, linux
Domain
observability-sre, operating-systems

Research direction

No source files, tests, or entry points are named in the issue. Start by locating the Linux syslog event-emission path and its configuration, then determine the scope of a direct socket option and how its behavior would be tested; done means events can be consumed directly without the described disk round trip.

Written by the indexing model from the issue text.

Description

enhancement

Writing events to syslog is inefficient as they hit the disk and then some other forwarding agent needs to read the back out from disk, parse the xml and forward the events.

On Windows we can use ETW to bypass the logging system anyway but on linux this is not an option as there is no system level mechanism to intercept syslog in a more efficient way.

Having logs fill up the disk when you are going to forward them anyway is kind of pointless too.

It would be nice to have an option where sysmon could open a unix domain socket (or maybe even a tcp socket) where other programs can just read events directly from there and not have the events being written to disk.

Dominant language
C
Stars
2.2k
Forks
220
Avg merge
11d 22h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/SysmonForLinux

All issues in microsoft/SysmonForLinux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.