package opentelemetry-cohttp-lwt
Install
Dune Dependency
Authors
Maintainers
Sources
sha256=281bb075de20663233709e67aec9dc95d75ec9b09a7e52e5c07557ff2cb89b17
sha512=4d7f07bd628dec23cb1b5171fe2012364b1720beb9cf3a5b74e9e6c0eae5777a0907deafdab08f18546c45b26eaf777ac9913753b1fa185b6554efe171595d8d
Description
Published: 16 Aug 2024
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
opentelemetry
should be used to instrument your code and possibly libraries. It doesn't communicate with anything except a backend (default: dummy backend)library
opentelemetry-client-ocurl
is a backend that communicates via http+protobuf with some collector (otelcol, datadog-agent, etc.)
License
MIT
Features
[x] basic traces
[x] basic metrics
[x] basic logs
[ ] nice API
[x] interface with
lwt
[x] sync collector relying on ocurl
[x] batching, perf, etc.
[ ] async collector relying on ocurl-multi
[ ] interface with
logs
(carry context around)[x] 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_setup
function.)
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_ENDPOINT
sets the http endpoint to send signals toOTEL_OCAML_DEBUG=1
to print some debug messages from the opentelemetry library ideOTEL_RESOURCE_ATTRIBUTES
sets 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)
-
cohttp-lwt
>= "4.0.0" & < "6.0.0~~"
-
lwt
>= "5.3"
-
opentelemetry-lwt
= version
-
opentelemetry
= version
-
ocaml
>= "4.08"
-
dune
>= "2.9"
Used by
None
Conflicts
None