serilog-sinks-seq
opentelemetry-collector-contrib
Our great sponsors
serilog-sinks-seq | opentelemetry-collector-contrib | |
---|---|---|
11 | 43 | |
210 | 2,546 | |
2.4% | 5.8% | |
6.0 | 10.0 | |
28 days ago | 4 days ago | |
C# | Go | |
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-collector-contrib
- OpenTelemetry at Scale: what buffer we can use at the behind to buffer the data?
-
All you need is Wide Events, not "Metrics, Logs and Traces"
The open telemetry collector does just that. https://github.com/open-telemetry/opentelemetry-collector-co...
-
OpenTelemetry Collector Anti-Patterns
There are two official distributions of the OpenTelemetry Collector: Core, and Contrib.
-
OpenTelemetry Journey #00 - Introduction to OpenTelemetry
Maybe, you are asking yourself: "But I already had instrumented my applications with vendor-specific libraries and I'm using their agents and monitoring tools, why should I change to OpenTelemetry?". The answer is: maybe you're right and I don't want to encourage you to update the way how you are doing observability in your applications, that's a hard and complex task. But, if you are starting from scratch or you are not happy with your current observability infrastructure, OpenTelemetry is the best choice, independently of the backend telemetry tool that you are using. I would like to invite you to take a look at the number of exporters available in the collector contrib section, if your backend tracing tool is not there, probably it's already using the Open Telemetry Protocol (OTLP) and you will be able to use the core collector. Otherwise, you should consider changing your backend telemetry tool or contributing to the project creating a new exporter.
-
Building an Observability Stack with Docker
To receive OTLP data, you set up the standard otlp receiver to receive data in HTTP or gRPC format. To forward traces and metrics, a batch processor was defined to accumulate data and send it every 100 milliseconds. Then set up a connection to Tempo (in otlp/tempo exporter, with a standard top exporter) and to Prometheus (in prometheus exporter, with a control exporter). A debug exporter also was added to log info on container standard I/O and see how the collector is working.
-
Spotlight: Sentry for Development
Thanks for the reply. Would the Spotlight sidecar possibly be able to run independently and consume spans emitted by the Sentry exporter[0] or some other similar flow beyond strictly exporting directly from the Sentry SDK provided by Spotlight?
This tooling looks really cool and I'd love to play around with it, but am already pretty entrenched into OTel and funneling data through the collector and don't want to introduce too much additional overhead for devs.
[0] https://github.com/open-telemetry/opentelemetry-collector-co...
-
Amazon EKS Monitoring with OpenTelemetry [Step By Step Guide]
A list of all metric definitions can be found here.
-
Spring Boot Monitoring with Open-Source Tools
receivers: otlp: protocols: grpc: endpoint: 0.0.0.0:4317 http: endpoint: 0.0.0.0:4318 hostmetrics: collection_interval: 60s scrapers: cpu: {} disk: {} load: {} filesystem: {} memory: {} network: {} paging: {} process: mute_process_name_error: true mute_process_exe_error: true mute_process_io_error: true processes: {} prometheus: config: global: scrape_interval: 60s scrape_configs: - job_name: otel-collector-binary scrape_interval: 60s static_configs: - targets: ["localhost:8889>"] - job_name: "jvm-metrics" scrape_interval: 10s metrics_path: "/actuator/prometheus" static_configs: - targets: ["localhost:8090>"] processors: batch: send_batch_size: 1000 timeout: 10s # Ref: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/resourcedetectionprocessor/README.md resourcedetection: detectors: [env, system] # Before system detector, include ec2 for AWS, gcp for GCP and azure for Azure. # Using OTEL_RESOURCE_ATTRIBUTES envvar, env detector adds custom labels. timeout: 2s system: hostname_sources: [os] # alternatively, use [dns,os] for setting FQDN as host.name and os as fallback extensions: health_check: {} zpages: {} exporters: otlp: endpoint: "ingest.{region}.signoz.cloud:443" tls: insecure: false headers: "signoz-access-token": logging: verbosity: normal service: telemetry: metrics: address: 0.0.0.0:8888 extensions: [health_check, zpages] pipelines: metrics: receivers: [otlp] processors: [batch] exporters: [otlp] metrics/internal: receivers: [prometheus, hostmetrics] processors: [resourcedetection, batch] exporters: [otlp] traces: receivers: [otlp] processors: [batch] exporters: [otlp] logs: receivers: [otlp] processors: [batch] exporters: [otlp]
-
Migrating to OpenTelemetry
If you are using the prometheus exporter, you can use the transform processor to get specific resource attributes into metric labels.
With the advantage that you get only the specific attributes you want, thus avoiding a cardinality explosion.
https://github.com/open-telemetry/opentelemetry-collector-co...
-
Exploring the OpenTelemetry Collector
OpenTelemetry Operators
What are some alternatives?
elmah.io - ELMAH error logger for sending errors to elmah.io.
uptrace - Open source APM: OpenTelemetry traces, metrics, and logs
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.
cockpit-podman - Cockpit UI for podman containers
dotnet-cloud-native-build-2023
signoz - SigNoz is an open-source observability platform native to OpenTelemetry with logs, traces and metrics in a single application. An open-source alternative to DataDog, NewRelic, etc. 🔥 🖥. 👉 Open source Application Performance Monitoring (APM) & Observability tool
tailon - Webapp for looking at and searching through files and streams. Fork of https://github.com/gvalkov/tailon
podman-compose - a script to run docker-compose.yml using podman
gotty - Share your terminal as a web application
traefik - The Cloud Native Application Proxy
Elasticsearch - Free and Open, Distributed, RESTful Search Engine
opentelemetry-collector-co