otel_logger_provider -> otel_logger
Details
The logger provider defines how logs are exported when collecting telemetry data. It is unlikely that you need to use logger provider objects directly.
Usually there is a single logger provider for an R app or script.
Typically the logger provider is created automatically, at the first
log()
call. otel decides which logger provider class to use based on
Environment Variables.
Implementations
Note that this list is updated manually and may be incomplete.
logger_provider_noop: No-op logger provider, used when no logs are emitted.
otelsdk::logger_provider_file: Save logs to a JSONL file.
otelsdk::logger_provider_http: Send logs to a collector over HTTP/OTLP.
otelsdk::logger_provider_stdstream: Write logs to standard output or error or to a file. Primarily for debugging.
Methods
logger_provider$get_logger()
Get or create a new logger object.
Usage
logger_provider$get_logger(
name = NULL,
version = NULL,
schema_url = NULL,
attributes = NULL
)
Arguments
name
Logger name. It makes sense to reuse the tracer name as the logger name. Seeget_logger()
anddefault_tracer_name()
.version
: Optional. Specifies the version of the instrumentation scope if the scope has a version (e.g. R package version). Example value:"1.0.0"
.schema_url
: Optional. Specifies the Schema URL that should be recorded in the emitted telemetry.attributes
: Optional. Specifies the instrumentation scope attributes to associate with emitted telemetry. Seeas_attributes()
for allowed values. You can also useas_attributes()
to convert R objects to OpenTelemetry attributes.
Value
An OpenTelemetry logger (otel_logger) object.
See also
Other low level logs API:
get_default_logger_provider()
,
get_logger()
,
logger_provider_noop
,
otel_logger
Examples
lp <- otel::get_default_logger_provider()
lgr <- lp$get_logger()
lgr$is_enabled()
#> [1] FALSE