OpenTelemetry Metrics

Beside the .NET runtime and ASP.NET Core metrics, Binacle.Net sends its own on two meters. Their names are experimental in 3.x - see Stability.

πŸ“¦ Packing

On the Binacle.Net meter, always on:

Metric Type Unit Attributes
binacle.packing.operation.duration histogram s operation, mode, request.algorithm; error.type on a failure
binacle.packing.operation.items histogram {item} operation, mode
binacle.packing.results counter {result} operation, mode, request.algorithm, result.algorithm, result.status

🏷️ Attributes

Each attribute key is under binacle.packing., such as binacle.packing.mode:

Attribute Values
operation fit, pack
mode single_bin, multiple_bins, smallest_bin, best_bin
request.algorithm ffd, wfd, bfd, or best when none is given
result.algorithm ffd, wfd, bfd - under best, the one that was picked
result.status fully_packed, partially_packed, not_packed, early_exit

πŸ“œ Packing Logs

With packing logs on, the Binacle.Net.DiagnosticsModule meter adds:

Metric Type Unit Shows
binacle.packing_log.processed counter {entry} every entry, by error.type
binacle.packing_log.queue.size up-down counter {entry} how full the queue is
binacle.packing_log.queue.capacity up-down counter {entry} the queue’s limit, only when ChannelLimit is set

error.type on binacle.packing_log.processed says what happened to the entry:

🩺 Health Checks

Requests to the health-check path are not counted in the HTTP request metrics, such as http.server.request.duration. Added in 3.2.0.