Add metrics and traces #111
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#111
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The idea here is to enable Garage cluster operators and developpers alike to benefit from observability feature, namely metrics and tracing, allowing them to better understand what is happening in a production cluster.
The current trending framework in this field is OpenTelemetry, an open data format that can be leveraged by multiple vendors.
On the metric side, the openmetrics format is very similar to the prometheus data format.
My proposition is to implement https://github.com/open-telemetry/opentelemetry-rust in garage, and:
Closing as OpenTelemetry has been implemented in Garage v0.7.0.