From 67bc9c87ef99dc13d93a1a6a48f96e17d0ec25b8 Mon Sep 17 00:00:00 2001 From: c-cube Date: Wed, 20 Apr 2022 16:47:44 +0000 Subject: [PATCH] deploy: 62f3bb8b03c41a3cfab44d76449ff8eb732d9c90 --- dev/opentelemetry/Opentelemetry/Collector/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev/opentelemetry/Opentelemetry/Collector/index.html b/dev/opentelemetry/Opentelemetry/Collector/index.html index ad437892..f266689f 100644 --- a/dev/opentelemetry/Opentelemetry/Collector/index.html +++ b/dev/opentelemetry/Opentelemetry/Collector/index.html @@ -2,4 +2,4 @@ Collector (opentelemetry.Opentelemetry.Collector)

Module Opentelemetry.Collector

Collector types

These types are used by backend implementations, to send events to collectors such as Jaeger.

Note: most users will not need to touch this module

type 'msg sender = {
send : 'a. 'msg -> ret:( unit -> 'a ) -> 'a;
}

Sender interface for a message of type msg. Inspired from Logs' reporter (see its doc) but without over as it doesn't make much sense in presence of batching.

The ret callback is used to return the desired type (unit, or a Lwt promise, or anything else) once the event has been transferred to the backend. It doesn't mean the event has been collected yet, it could sit in a batch queue for a little while.

module type BACKEND = sig ... end

Collector client interface.

type backend = (module BACKEND)
val backend : backend option Stdlib.ref
val has_backend : unit -> bool

Is there a configured backend?

val send_trace : Proto.Trace.resource_spans list -> ret:( unit -> 'a ) -> 'a
val send_metrics : Proto.Metrics.resource_metrics list -> ret:( unit -> 'a ) -> - 'a
val rand_bytes_16 : unit -> bytes
val rand_bytes_8 : unit -> bytes
\ No newline at end of file + 'a
val rand_bytes_16 : unit -> bytes
val rand_bytes_8 : unit -> bytes
val tick : unit -> unit

Do background work. Call this regularly if the collector doesn't already have a ticker thread or internal timer.

\ No newline at end of file