What happens to your data when a receiver endpoint of the OpenTelemetry Controller becomes unavailable? Read about different scenarios and mitigation options.
How to solve hard and soft multi-tenancy scenarios in Kubernetes using the Logging operator and the Telemetry controller
The Telemetry Controller turns telemetry event streams – logs, metrics, and traces – into Kubernetes resources. It provides a multi-tenant API on top of OpenTelemetry for isolation and access control for telemetry data.
Forward your Kubernetes logs to OpenObserve with syslog-ng and the Logging operator using AxoSyslog, the cloud-native syslog-ng distribution
Packet drops and buffering in syslog and observability pipelines
Collect logs from the native macOS OSlog or log stream with syslog-ng’s new darwin-os sources!
syslog-ng 4.6 allows you to send data directly to Google BigQuery, better collect logs on macOS, parse Windows XML logs, and improves OpenTelemetry performance
Learn how to create usable log messages by configuring log severity levels, with special focus on Python, OpenTelemetry, and syslog log levels.
syslog-ng in 2023: new features (OpenTelemetry, Google Pub/Sub, Splunk, Grafana Loki, Amazon S3, OpenObserve drivers), contributions, and other developments
Forward your Kubernetes logs to Grafana Loki with syslog-ng and the Logging operator using AxoSyslog, the cloud-native syslog-ng distribution
Send logs and telemetry data directly to Google BigQuery with syslog-ng, using gRPC
Solving logging in multi-tenant scenarios in Kubernetes is not always easy. Here is how Logging operator can help you.
syslog-ng 4.5 integrates your telemetry pipeline to Google Pub/Sub and OpenObserve
Logging operator is now a CNCF sandbox project – how does it affect you, and what are the future plans for Logging operator? What is a Telemetry Pipeline for Kubernetes?