package opentelemetry
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>
Instrumentation for https://opentelemetry.io
Install
dune-project
Dependency
Authors
Maintainers
Sources
opentelemetry-0.13.tbz
sha256=e29a0aa7168357ebbed0f50b1ba9374bc277b280935531e77d90183c732b98f6
sha512=2fd9dcf03695be7b7888c5fb3d0dbe2acdcfbb7c99dfa7b2ff2fc0bb626c4e35ec8d2be71632e440b9df1cc79529c5258ca98876a373a41cff48e4b1757c5767
doc/opentelemetry.client/Opentelemetry_client/Signal/index.html
Module Opentelemetry_client.SignalSource
Constructing and managing OTel signals
Source
type t = | Traces of Opentelemetry_proto.Trace.resource_spans list| Metrics of Opentelemetry_proto.Metrics.resource_metrics list| Logs of Opentelemetry_proto.Logs.resource_logs list
The type of signals
This is not the principle type of signals from the perspective of what gets encoded and sent via protocl buffers, but it is the principle type that collector clients needs to reason about.
Encode signals to protobuf encoded strings, ready to be sent over the wire
Decode signals from protobuf encoded strings, received over the wire
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>