opentelemetry-rust/opentelemetry-appender-log
Cijo Thomas ff33638d1e
feat: Allow event name to be provided to IsEnabled check in Logger (#2756)
2025-03-04 15:39:58 -08:00
..
examples Rename LoggerProvider, Logger to SdkLoggerProvider, SdkLogger (#2612) 2025-02-05 07:37:45 -08:00
src feat: Allow event name to be provided to IsEnabled check in Logger (#2756) 2025-03-04 15:39:58 -08:00
CHANGELOG.md Prepare v0.28.0 (#2635) 2025-02-10 09:52:55 -08:00
Cargo.toml Avoid duplicate crates (#2703) 2025-02-25 08:07:55 -08:00
LICENSE fix: revert modifications to Apache license (#1664) 2024-04-18 16:30:52 -07:00
README.md Fix 2638: Use absolute URL for LICENSE/CHANGELOG in README (#2682) 2025-02-18 19:00:29 -08:00

README.md

OpenTelemetry Log Appender for log crate

OpenTelemetry — An observability framework for cloud-native software.

This crate contains a Log Appender that bridges logs from the log crate to OpenTelemetry.

Crates.io: opentelemetry-appender-log Documentation LICENSE GitHub Actions CI Slack

OpenTelemetry Overview

OpenTelemetry is an Observability framework and toolkit designed to create and manage telemetry data such as traces, metrics, and logs. OpenTelemetry is vendor- and tool-agnostic, meaning that it can be used with a broad variety of Observability backends, including open source tools like [Jaeger] and [Prometheus], as well as commercial offerings.

OpenTelemetry is not an observability backend like Jaeger, Prometheus, or other commercial vendors. OpenTelemetry is focused on the generation, collection, management, and export of telemetry. A major goal of OpenTelemetry is that you can easily instrument your applications or systems, no matter their language, infrastructure, or runtime environment. Crucially, the storage and visualization of telemetry is intentionally left to other tools.

Release Notes

You can find the release notes (changelog) here.