otel_logger_provider -> otel_logger
Not applicable.
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.
logger_provider$get_logger()
Get or create a new logger object.
logger_provider$get_logger(
name = NULL,
version = NULL,
schema_url = NULL,
attributes = NULL
)
name Logger name. It makes sense to reuse the tracer name as the
logger name. See get_logger() and default_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. See as_attributes()
for allowed values. You can also use as_attributes() to convert R
objects to OpenTelemetry attributes.
An OpenTelemetry logger (otel_logger) object.
get_default_logger_provider(), get_logger().
logger_provider$flush()
Force any buffered logs to flush. Logger providers might not implement this method.
logger_provider$flush()
Nothing.
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.
Other low level logs API:
get_default_logger_provider(),
get_logger(),
logger_provider_noop,
otel_logger
lp <- otel::get_default_logger_provider()
lgr <- lp$get_logger()
lgr$is_enabled()
Run the code above in your browser using DataLab