package opentelemetry-lwt
Install
    
    dune-project
 Dependency
Authors
Maintainers
Sources
sha256=400e6fcaff55b92e65d5c082d0262a7c2fc91b385dac0f18ed28405db2669978
    
    
  sha512=9f4d2329dec682bb2a839d1c7065f35bc557fc8ef5996c5923cf05af716e6519b0ce66316687e74232cf93baa5c1df4899d1bdd4b4f4b44468bb8b3f57619913
    
    
  Description
README
Opentelemetry 
This project provides an API for instrumenting server software using opentelemetry, as well as connectors to talk to opentelemetry software such as jaeger.
- library 
opentelemetryshould be used to instrument your code and possibly libraries. It doesn't communicate with anything except a backend (default: dummy backend) - library 
opentelemetry-client-ocurlis a backend that communicates via http+protobuf with some collector (otelcol, datadog-agent, etc.) 
License
MIT
Features
- basic traces
 - basic metrics
 - basic logs
 - nice API
 - interface with 
lwt - sync collector relying on ocurl
 
- batching, perf, etc.
 
- async collector relying on ocurl-multi
 - interface with 
logs(carry context around) - implicit scope (via ambient-context)
 
Use
For now, instrument traces/spans, logs, and metrics manually:
module Otel = Opentelemetry
let (let@) f x = f x
let foo () =
  let@ scope = Otel.Trace.with_  "foo"
      ~attrs:["hello", `String "world"] in
  do_work();
  Otel.Metrics.(
    emit [
      gauge ~name:"foo.x" [int 42];
    ]);
  do_more_work();
  ()Setup
If you're writing a top-level application, you need to perform some initial configuration.
- Set the 
service_name; - configure our ambient-context dependency with the appropriate storage for your environment — TLS, Lwt, Eio ... (see their docs for more details);
 - and install a 
Collector(usually by calling your collector'swith_setupfunction.) 
For example, if your application is using Lwt, and you're using ocurl as your collector, you might do something like this:
let main () =
  Otel.Globals.service_name := "my_service";
  Otel.GC_metrics.basic_setup();
  Ambient_context.with_storage_provider (Ambient_context_lwt.storage ()) @@ fun () ->
  Opentelemetry_client_ocurl.with_setup () @@ fun () ->
  (* … *)
  foo ();
  (* … *)Configuration
The library is configurable via Opentelemetry.Config, via the standard opentelemetry env variables, or with some custom environment variables.
OTEL_EXPORTER_OTLP_ENDPOINTsets the http endpoint to send signals toOTEL_OCAML_DEBUG=1to print some debug messages from the opentelemetry library ideOTEL_RESOURCE_ATTRIBUTESsets a comma separated list of custom resource attributes
Collector opentelemetry-client-ocurl
This is a synchronous collector that uses the http+protobuf format to send signals (metrics, traces, logs) to some other collector (eg. otelcol or the datadog agent).
Collector opentelemetry-client-cohttp-lwt
This is a Lwt-friendly collector that uses cohttp to send signals to some other collector (e.g. otelcol). It must be run inside a Lwt_main.run scope.
Opentelemetry-trace
The optional library opentelemetry.trace, present if trace is installed, provides a collector for trace. This collector forwards and translates events from trace into opentelemetry. It's only useful if there also is also a OTEL collector.
License
MIT
Semantic Conventions
Not supported yet.
Dependencies (6)
- 
  
    lwt_ppx
  
  
    
>= "2.0" - 
  
    lwt
  
  
    
>= "5.3" - 
  
    opentelemetry
  
  
    
= version - ambient-context
 - 
  
    ocaml
  
  
    
>= "4.08" - 
  
    dune
  
  
    
>= "2.9" 
Dev Dependencies (3)
- 
  
    alcotest
  
  
    
with-test - 
  
    odoc
  
  
    
with-doc - 
  
    cohttp-lwt-unix
  
  
    
with-test 
Used by (1)
- 
  
    opentelemetry-cohttp-lwt
  
  
    
= "0.9" 
Conflicts
None