serilog-sinks-seq
opentelemetry-dotnet
Our great sponsors
serilog-sinks-seq | opentelemetry-dotnet | |
---|---|---|
11 | 7 | |
210 | 2,961 | |
2.4% | 3.3% | |
6.0 | 9.7 | |
28 days ago | 7 days ago | |
C# | C# | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
serilog-sinks-seq
-
Graylog deployment help
I dont know why you want to use Graylog, but just fyi maybe https://datalust.co/seq is a alternative.
- ASP.NET Core: Monitoreo con OpenTelemetry y Grafana
-
Question: monitoring cloud product deployed in customer’s own subscription.
You could use something like Seq to stream all the logs back to you.
-
Ask HN: Lightweight ELK alternative for ingesting and analyzing local logs?
Valuable related discussion: https://www.reddit.com/r/devops/comments/13ab0l5/lightweight...
Highlights:
* Grafana and Loki seems to be favorite
* https://datalust.co/seq is the easiest to deploy (single container)
* https://github.com/tstack/lnav CLI based tool
-
Elastic, Loki and SigNoz – A Perf Benchmark of Open-Source Logging Platforms
https://datalust.co/seq (my employer) uses a custom database built with Rust. We are about to remove the last C# database code because, as the previous commenter noted, garbage collection and databases don't mix.
Over the next few years I expect we will see a lot of new databases written in Rust.
https://blog.datalust.co/what-will-seq-vnext-look-like-on-th...
-
Simple way to centralize my server logs?
I know I’m a little late to the game, but check out Seq. If you use Docker, you can deploy Seq and Seq-input-gelf Docker containers, set gelf as the default logging driver in your daemon.json, and point it at you Seq instance. That’s pretty much it. Seq also accepts a bunch of other log inputs, like Greylog, for things that don’t run in Docker.
-
Embrace the Power of Structured Logging
There are several popular logging servers that store and process structured log data. The ones I currently know are SigNoz, Seq, New Relic and Kibana. The latter is, in a nutshell, a user interface to visualize Elasticsearch data.
-
Simple remote log storage service?
Another for Seq.
-
What is a tool you use or a bit of code that you like to use that you feel is worth bragging about?
Seq for centralized logging in both development and production environments https://datalust.co/seq
-
Opensource or free log analysers
Seq has a free option for individuals - https://datalust.co/seq
opentelemetry-dotnet
-
ASP.NET Core: Monitoreo con OpenTelemetry y Grafana
open-telemetry/opentelemetry-dotnet: The OpenTelemetry .NET Client (github.com)
-
Guide to Distributed Tracing with OpenTelemetry Dotnet
💡Good to know -- If you wish to export traces to Jaeger, you should use the AddJaegerExporter instead of the AddOtlpExporter. Visit the opentelemetry-dotnet repository to see how it's done.
-
Observability with Grafana Cloud and OpenTelemetry in .net microservices
We're going to use OpenTelemetry .NET SDK. Add following nuget dependencies to the project:
-
OpenTelemetry in Action: Identifying Database Dependencies
We instrument the application with the OpenTelemetry SDK and SqlClient instrumentation library for .NET. First, we add the following NuGet package references to the API’s project file:
-
State for each API Request
It should be handled automatically by OpenTelemetry middlewares. Just look through documentation and samples https://github.com/open-telemetry/opentelemetry-dotnet
-
[c#] Using W3C Trace Context standard in distributed tracing
Besides that, the propagation fields (traceparent and tracestate) were added in the message header. In the last article, I said that the standard (in the Working Draft (WD) step of the w3c process) recommends to add the propagation fields in the application-properties section by the message publisher. For the current example, I chose to propagate that context in the message header even for AMQP calls as was done in the dotnet OpenTelemetry example. It's important to reinforce that Trace Context: AMQP protocol is not a W3C Recommendation yet. Take a look at the place where the propagation fields were added:
-
Tracing End-to-End Data from Power Apps to Azure Cosmos DB
As long as the Azure Functions app knows the instrumentation key from an Application Insights instance, it traces almost everything. OpenTelemetry.NET is one of the Open Telemetry implementations, has recently released v1.0 for tracing. Both metrics and logging are close to GA. However, it doesn't work well with Azure Functions. Therefore, in this post, let's manually implement the tracing at the log level, which is sent to Application Insights.
What are some alternatives?
opentelemetry-collector-contrib - Contrib repository for the OpenTelemetry Collector
ApplicationInsights-dotnet - ApplicationInsights-dotnet
elmah.io - ELMAH error logger for sending errors to elmah.io.
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
Testura.Code - Testura.Code is a wrapper around the Roslyn API and used for generation, saving and compiling C# code. It provides methods and helpers to generate classes, methods, statements and expressions.
zipkin - Zipkin is a distributed tracing system
dotnet-cloud-native-build-2023
C# StatsD Client
tailon - Webapp for looking at and searching through files and streams. Fork of https://github.com/gvalkov/tailon
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
gotty - Share your terminal as a web application
trace-context-w3c - W3C Trace Context purpose of and what kind of problem it came to solve.