package opentelemetry

You can search for identifiers within the package.

in-package search v0.2.0

opentelemetry
- Opentelemetry
  - Collector
    
    BACKEND
  - Conventions
    
    Attributes
    
    Process
    
    Runtime
    
    Service
    
    Metrics
    
    Process
    
    Runtime
    
    Ocaml
    
    GC
  - Event
  - GC_metrics
  - Globals
  - Lock
  - Logs
  - Metrics
  - Metrics_callbacks
  - Proto
    
    Common
    
    Logs
    
    Logs_service
    
    Metrics
    
    Metrics_service
    
    Resource
    
    Status
    
    Trace
    
    Trace_service
  - Rand_bytes
  - Scope
  - Span
  - Span_id
  - Span_link
  - Thread_local
  - Timestamp_ns
  - Trace
  - Trace_context
    
    Traceparent
  - Trace_id
  - Util_
opentelemetry.atomic
- Opentelemetry_atomic
  - Atomic

Legend:
Library
Module
Module type
Parameter
Class
Class type

Process-wide metadata, environment variables, etc.

val service_name : string Stdlib.ref

Main service name metadata

val service_namespace : string option Stdlib.ref

Namespace for the service

val service_instance_id : string option Stdlib.ref

Unique identifier for the service

val instrumentation_library : Proto.Common.instrumentation_scope

val global_attributes : Proto.Common.key_value list Stdlib.ref

Global attributes, initially set via OTEL_RESOURCE_ATTRIBUTES and modifiable by the user code. They will be attached to each outgoing metrics/traces.

val add_global_attribute : string -> value -> unit

Add a global attribute

val merge_global_attributes_ : 
  Proto.Common.key_value list ->
  Proto.Common.key_value list

val default_span_kind : Proto.Trace.span_span_kind Stdlib.ref

Default span kind in Span.create. This will be used in all spans that do not specify ~kind explicitly. It can be convenient to set "client" or "server" uniformly in here.

since 0.4

val mk_attributes : 
  ?service_name:string ->
  ?attrs:
    (string * [< `Bool of bool | `Int of int | `None | `String of string ])
      list ->
  unit ->
  Proto.Common.key_value list