serilog-sinks-http | A Serilog sink sending log events over HTTP

by FantasticFiasco C# Version: v8.0.0 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | serilog-sinks-http Summary

serilog-sinks-http is a C# library. serilog-sinks-http has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

This project started out with a wish to send log events to the Elastic Stack. I had prior experience of Elastic Filebeat and didn't like it. I thought the value it added was lower than the complexity it introduced. Knowing that Serilog.Sinks.Seq existed, and knowing that the code was of really good quality, I blatantly copied many of the core files into this project and started developing a general HTTP sink. And here we are today. I hope you'll find the sink useful. If not, don't hesitate to open an issue.

Support

Quality

Security

License

Reuse

Support

serilog-sinks-http has a low active ecosystem.

It has 138 star(s) with 38 fork(s). There are 6 watchers for this library.

It had no major release in the last 12 months.

There are 10 open issues and 92 have been closed. On average issues are closed in 66 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of serilog-sinks-http is v8.0.0

Quality

serilog-sinks-http has 0 bugs and 0 code smells.

Security

serilog-sinks-http has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

serilog-sinks-http code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

serilog-sinks-http is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

serilog-sinks-http releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of serilog-sinks-http

Get all kandi verified functions for this library.

serilog-sinks-http Key Features

No Key Features are available at this moment for serilog-sinks-http.

serilog-sinks-http Examples and Code Snippets

No Code Snippets are available at this moment for serilog-sinks-http.

Community Discussions

Trending Discussions on serilog-sinks-http

Serilog-Sinks-Loki transmitting logs to Loki in big batches. How can I reduce batch amount?

QUESTION

Serilog-Sinks-Loki transmitting logs to Loki in big batches. How can I reduce batch amount?

Asked 2020-Oct-21 at 23:27

I am trying to send my logs from .netcore 3.1 API to Loki server. For doing that I'm using Serilog-Sinks-Loki nugget package. When I run my code, logs are sent immediately and I can see them in Grafana. As time past, logs are coming with delay which growing bigger and bigger. Eventually I see my logs arriving after delay of 10 minutes to Loki. I read about that and understand that Serilog-Sinks-Loki sits on top of Serilog-Sinks-Http so I need to configure something over there to make my logs arrive faster but not sure how, can someone help me with that please? My goal is to send my logs immediately, with no delay.

Here is my program.cs code

...

ANSWER

Answered 2020-Oct-21 at 23:27

Although Serilog.Sinks.Loki wraps a Serilog.Sinks.Http sink, it doesn't expose any of the settings that would allow you to configure how often messages are sent (batchPostingLimit, period, etc.)

That said, the default period of Sinks.Sink.Http is 2 seconds, thus 10 minutes is too long for messages to be sent with the default settings. You're likely having connection issues that are blocking the sink from sending the messages or blocking the server from receiving them.

Have you tried enabling the SelfLog to see if any errors are being caught by the sink?

If not, you can monitor the network traffic to see if you can find failed attempts and/or timeouts when the sink tries to send the log events.

You can also extend the LokiHttpClient and write some debug messages to a file or something to see how often / how many messages are being sent.

For reference here is a recent issue in the Serilog.Sinks.Loki repo (perhaps you created it?)

Logs are been sent as a batch once in 10 minutes #26

Source https://stackoverflow.com/questions/64472313

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install serilog-sinks-http

If you want to include the HTTP sink in your project, you can install it directly from NuGet.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: