https://github.com/fantasticfiasco/serilog-sinks-http-sample-fluentd

Sample application of Serilog.Sinks.Http sending log events to Fluentd.
https://github.com/fantasticfiasco/serilog-sinks-http-sample-fluentd

dotnet fluentd http serilog serilog-sink

Last synced: 13 days ago
JSON representation

Sample application of Serilog.Sinks.Http sending log events to Fluentd.

• Host: GitHub
• URL: https://github.com/fantasticfiasco/serilog-sinks-http-sample-fluentd
• Owner: FantasticFiasco
• License: apache-2.0
• Created: 2019-11-19T22:13:56.000Z (about 5 years ago)
• Default Branch: master
• Last Pushed: 2024-12-02T06:30:27.000Z (about 1 month ago)
• Last Synced: 2024-12-02T07:28:24.905Z (about 1 month ago)
• Topics: dotnet, fluentd, http, serilog, serilog-sink
• Language: C#
• Homepage:
• Size: 193 KB
• Stars: 1
• Watchers: 3
• Forks: 0
• Open Issues: 7
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Serilog and Fluentd

## Introduction

[Fluentd](https://www.fluentd.org/) is an open source data collector providing a unified logging layer. [Serilog](https://serilog.net/) is fantastic at producing structured log events. This repository provides a sandbox where developers can explore the life of a log event starting with its birth in Serilog, its transport over the network using HTTP, and finally being collected and processed by Fluentd.

## What you will end up with

![alt text](./assets/console.png "Fluentd stdout showing log events")

With a running Fluentd server and Serilog producing log events you are now ready to take it to the next level. If you fancy the producing part you'll dig deeper into Serilog and its configuration of log contexts, enrichers and message formatters. If you enjoy configuring data collectors you'll explore Fluentd with its inputs, filters and outputs.

## Requirements

- [Docker](https://www.docker.com/community-edition#/download)

- [Docker Compose](https://docs.docker.com/compose/install)

## Usage

Start two services, one producing log events and one consuming them, with the following command.

```posh

docker compose up

```