diff --git a/dev/opentelemetry-client-ocurl/Opentelemetry_client_ocurl/index.html b/dev/opentelemetry-client-ocurl/Opentelemetry_client_ocurl/index.html index a95083f6..3b5b9b89 100644 --- a/dev/opentelemetry-client-ocurl/Opentelemetry_client_ocurl/index.html +++ b/dev/opentelemetry-client-ocurl/Opentelemetry_client_ocurl/index.html @@ -1,5 +1,9 @@ -
Opentelemetry_client_ocurlUrl of the endpoint. Default is "http://localhost:4318", or "OTEL_EXPORTER_OTLP_ENDPOINT" if set.
Set http headers that are sent on every http query to the collector.
module Atomic = Opentelemetry_atomic.Atomicmodule Config : sig ... endConfiguration for the ocurl backend
val setup :
+Opentelemetry_client_ocurl (opentelemetry-client-ocurl.Opentelemetry_client_ocurl) Module Opentelemetry_client_ocurl
Url of the endpoint. Default is "http://localhost:4318", or "OTEL_EXPORTER_OTLP_ENDPOINT" if set.
Set http headers that are sent on every http query to the collector.
module Atomic = Opentelemetry_atomic.Atomicmodule Config : sig ... endConfiguration for the ocurl backend
val create_backend :
+ ?stop:bool Atomic.t ->
+ ?config:Config.t ->
+ unit ->
+ (module Opentelemetry.Collector.BACKEND)val setup :
?stop:bool Atomic.t ->
?config:Config.t ->
?enable:bool ->
diff --git a/dev/opentelemetry-lwt/Opentelemetry_lwt/Logs/index.html b/dev/opentelemetry-lwt/Opentelemetry_lwt/Logs/index.html
index e2ba503b..9583c66d 100644
--- a/dev/opentelemetry-lwt/Opentelemetry_lwt/Logs/index.html
+++ b/dev/opentelemetry-lwt/Opentelemetry_lwt/Logs/index.html
@@ -99,7 +99,12 @@
'aMake a log entry with format
val emit :
?service_name:string ->
?attrs:
- (string * [< `Bool of bool | `Int of int | `None | `String of string ])
+ (string
+ * [< `Bool of bool
+ | `Float of float
+ | `Int of int
+ | `None
+ | `String of string ])
list ->
t list ->
unitEmit logs.
This instructs the collector to send the logs to some backend at a later date. NOTE be careful not to call this inside a Gc alarm, as it can cause deadlocks.
Number data point, as a float
val int :
?start_time_unix_nano:Opentelemetry.Timestamp_ns.t ->
?now:Opentelemetry.Timestamp_ns.t ->
?attrs:
- (string * [< `Bool of bool | `Int of int | `None | `String of string ])
+ (string
+ * [< `Bool of bool
+ | `Float of float
+ | `Int of int
+ | `None
+ | `String of string ])
list ->
int ->
Opentelemetry__.Metrics_types.number_data_pointNumber data point, as an int
val gauge :
@@ -29,7 +39,12 @@
?start_time_unix_nano:Opentelemetry.Timestamp_ns.t ->
?now:Opentelemetry.Timestamp_ns.t ->
?attrs:
- (string * [< `Bool of bool | `Int of int | `None | `String of string ])
+ (string
+ * [< `Bool of bool
+ | `Float of float
+ | `Int of int
+ | `None
+ | `String of string ])
list ->
?exemplars:Opentelemetry__.Metrics_types.exemplar list ->
?explicit_bounds:float list ->
@@ -47,12 +62,22 @@
tval make_resource_metrics :
?service_name:string ->
?attrs:
- (string * [< `Bool of bool | `Int of int | `None | `String of string ])
+ (string
+ * [< `Bool of bool
+ | `Float of float
+ | `Int of int
+ | `None
+ | `String of string ])
list ->
t list ->
Opentelemetry__.Metrics_types.resource_metricsAggregate metrics into a Proto.Metrics.resource_metrics
val emit :
?attrs:
- (string * [< `Bool of bool | `Int of int | `None | `String of string ])
+ (string
+ * [< `Bool of bool
+ | `Float of float
+ | `Int of int
+ | `None
+ | `String of string ])
list ->
t list ->
unitEmit some metrics to the collector (sync). This blocks until the backend has pushed the metrics into some internal queue, or discarded them.
NOTE be careful not to call this inside a Gc alarm, as it can cause deadlocks.
Opentelemetry_lwt.Traceinclude module type of struct include Opentelemetry.Trace endTraces.
See the spec
type span = Opentelemetry.Span.tval make_resource_spans :
?service_name:string ->
?attrs:
- (string * [< `Bool of bool | `Int of int | `None | `String of string ])
+ (string
+ * [< `Bool of bool
+ | `Float of float
+ | `Int of int
+ | `None
+ | `String of string ])
list ->
Opentelemetry.Proto.Trace.span list ->
Opentelemetry.Proto.Trace.resource_spansval emit :
?service_name:string ->
?attrs:
- (string * [< `Bool of bool | `Int of int | `None | `String of string ])
+ (string
+ * [< `Bool of bool
+ | `Float of float
+ | `Int of int
+ | `None
+ | `String of string ])
list ->
span list ->
unitSync emitter.
This instructs the collector to forward the spans to some backend at a later point.
NOTE be careful not to call this inside a Gc alarm, as it can cause deadlocks.
type scope = Opentelemetry.Scope.t = {trace_id : Opentelemetry.Trace_id.t;span_id : Opentelemetry.Span_id.t;mutable events : Opentelemetry.Event.t list;mutable attrs : Opentelemetry.Span.key_value list;}val add_attrs :
Opentelemetry.Scope.t ->
(unit -> Opentelemetry.key_value list) ->
- unitval with_' :
+ ?force_new_trace_id:bool ->
?trace_state:string ->
?service_name:string ->
- ?attrs:Opentelemetry.Span.key_value list ->
- ?kind:Span.kind ->
- ?trace_id:Trace_id.t ->
- ?parent:Span.id ->
- ?scope:scope ->
+ ?attrs:(string * Opentelemetry.value) list ->
+ ?kind:Opentelemetry.Span.kind ->
+ ?trace_id:Opentelemetry.Trace_id.t ->
+ ?parent:Opentelemetry.Span.id ->
+ ?scope:Opentelemetry.Scope.t ->
+ ?links:Opentelemetry.Span_link.t list ->
+ string ->
+ (scope -> 'a) ->
+ (unit -> 'a) * ((unit, string) Stdlib.result -> unit)Sync span guard.
Notably, this includes implicit scope-tracking: if called without a ~scope argument (or ~parent/~trace_id), it will check in the Ambient_context for a surrounding environment, and use that as the scope. Similarly, it uses Scope.with_ambient_scope to set a new scope in the ambient context, so that any logically-nested calls to with_ will use this span as their parent.
NOTE be careful not to call this inside a Gc alarm, as it can cause deadlocks.
val with_ :
+ ?force_new_trace_id:bool ->
+ ?trace_state:string ->
+ ?service_name:string ->
+ ?attrs:(string * Opentelemetry.value) list ->
+ ?kind:Opentelemetry.Span.kind ->
+ ?trace_id:Opentelemetry.Trace_id.t ->
+ ?parent:Opentelemetry.Span.id ->
+ ?scope:Opentelemetry.Scope.t ->
?links:Opentelemetry.Span_link.t list ->
string ->
(Opentelemetry.Scope.t -> 'a Lwt.t) ->
diff --git a/dev/opentelemetry/Opentelemetry/Collector/Debug_backend/argument-1-B/index.html b/dev/opentelemetry/Opentelemetry/Collector/Debug_backend/argument-1-B/index.html
new file mode 100644
index 00000000..b97bb9ea
--- /dev/null
+++ b/dev/opentelemetry/Opentelemetry/Collector/Debug_backend/argument-1-B/index.html
@@ -0,0 +1,2 @@
+
+B (opentelemetry.Opentelemetry.Collector.Debug_backend.B) Parameter Debug_backend.B
val send_trace : Proto.Trace.resource_spans list senderval send_metrics : Proto.Metrics.resource_metrics list senderval send_logs : Proto.Logs.resource_logs list senderSignal the backend that it should emit GC metrics when it has the chance. This should be installed in a GC alarm or another form of regular trigger.
Give the collector the list of callbacks to be executed when tick() is called. Each such callback should be short and reentrant. Depending on the collector's implementation, it might be called from a thread that is not the one that called on_tick.
\ No newline at end of file
diff --git a/dev/opentelemetry/Opentelemetry/Collector/Debug_backend/index.html b/dev/opentelemetry/Opentelemetry/Collector/Debug_backend/index.html
new file mode 100644
index 00000000..33517044
--- /dev/null
+++ b/dev/opentelemetry/Opentelemetry/Collector/Debug_backend/index.html
@@ -0,0 +1,2 @@
+
+Debug_backend (opentelemetry.Opentelemetry.Collector.Debug_backend) Module Collector.Debug_backend
Parameters
Signature
val send_trace : Proto.Trace.resource_spans list senderval send_metrics : Proto.Metrics.resource_metrics list senderval send_logs : Proto.Logs.resource_logs list senderSignal the backend that it should emit GC metrics when it has the chance. This should be installed in a GC alarm or another form of regular trigger.
Give the collector the list of callbacks to be executed when tick() is called. Each such callback should be short and reentrant. Depending on the collector's implementation, it might be called from a thread that is not the one that called on_tick.
\ No newline at end of file
diff --git a/dev/opentelemetry/Opentelemetry/Collector/Noop_backend/index.html b/dev/opentelemetry/Opentelemetry/Collector/Noop_backend/index.html
new file mode 100644
index 00000000..cf4544ed
--- /dev/null
+++ b/dev/opentelemetry/Opentelemetry/Collector/Noop_backend/index.html
@@ -0,0 +1,2 @@
+
+Noop_backend (opentelemetry.Opentelemetry.Collector.Noop_backend) Module Collector.Noop_backend
val send_trace : Proto.Trace.resource_spans list senderval send_metrics : Proto.Metrics.resource_metrics list senderval send_logs : Proto.Logs.resource_logs list senderSignal the backend that it should emit GC metrics when it has the chance. This should be installed in a GC alarm or another form of regular trigger.
Give the collector the list of callbacks to be executed when tick() is called. Each such callback should be short and reentrant. Depending on the collector's implementation, it might be called from a thread that is not the one that called on_tick.
\ No newline at end of file
diff --git a/dev/opentelemetry/Opentelemetry/Collector/index.html b/dev/opentelemetry/Opentelemetry/Collector/index.html
index 9b03892f..08a7ce92 100644
--- a/dev/opentelemetry/Opentelemetry/Collector/index.html
+++ b/dev/opentelemetry/Opentelemetry/Collector/index.html
@@ -1,5 +1,10 @@
-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
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 ... endCollector client interface.
type backend = (module BACKEND)val set_backend : backend -> unitSet collector backend
val get_backend : unit -> backend optionCurrent backend, if any
val send_trace : Proto.Trace.resource_spans list -> ret:(unit -> 'a) -> 'aval send_metrics :
+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
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 ... endCollector client interface.
type backend = (module BACKEND)module Noop_backend : BACKENDmodule Debug_backend (B : BACKEND) : BACKENDval debug_backend : backendval set_backend : backend -> unitSet collector backend
val get_backend : unit -> backend optionCurrent backend, if any
val send_trace : Proto.Trace.resource_spans list -> ret:(unit -> 'a) -> 'aval send_metrics :
Proto.Metrics.resource_metrics list ->
ret:(unit -> 'a) ->
- 'aval send_logs : Proto.Logs.resource_logs list -> ret:(unit -> 'a) -> 'a
\ No newline at end of file
+ 'aval send_logs : Proto.Logs.resource_logs list -> ret:(unit -> 'a) -> 'aDo background work. Call this regularly if the collector doesn't already have a ticker thread or internal timer.
val with_setup_debug_backend :
+ backend ->
+ ?enable:bool ->
+ unit ->
+ (unit -> 'a) ->
+ 'a
\ No newline at end of file
diff --git a/dev/opentelemetry/Opentelemetry/Globals/index.html b/dev/opentelemetry/Opentelemetry/Globals/index.html
index 7230c133..9b77a5c9 100644
--- a/dev/opentelemetry/Opentelemetry/Globals/index.html
+++ b/dev/opentelemetry/Opentelemetry/Globals/index.html
@@ -4,7 +4,12 @@
Proto.Common.key_value listval default_span_kind : Proto.Trace.span_span_kind Stdlib.refDefault span kind in Span.create. This will be used in all spans that do not specify ~kind explicitly; it is set to "internal", following directions from the .proto file. It can be convenient to set "client" or "server" uniformly in here.
val mk_attributes :
?service_name:string ->
?attrs:
- (string * [< `Bool of bool | `Int of int | `None | `String of string ])
+ (string
+ * [< `Bool of bool
+ | `Float of float
+ | `Int of int
+ | `None
+ | `String of string ])
list ->
unit ->
Proto.Common.key_value listMake a log entry with format
val emit :
?service_name:string ->
?attrs:
- (string * [< `Bool of bool | `Int of int | `None | `String of string ])
+ (string
+ * [< `Bool of bool
+ | `Float of float
+ | `Int of int
+ | `None
+ | `String of string ])
list ->
t list ->
unitEmit logs.
This instructs the collector to send the logs to some backend at a later date. NOTE be careful not to call this inside a Gc alarm, as it can cause deadlocks.