v0.27.51
Changes
docs: document data client latency metric (#4180)
Description
This PR documents the data client runtime timing metrics introduced in
#4087 in the operations guide (docs/operation/operation.md). These
metrics measure execution time for loading initial routes and applying
incremental route updates across data clients, providing better
observability into route sync latency.
cc @MustafaSaber, please take a look when you get a chance!
Changes
Added documentation under ## Monitoring -> ### Data client metrics
for:
routes.load_all.<client>: Timer measuring execution time for loading
all routes from the data client.routes.load_update.<client>: Timer measuring execution time for
loading incremental route updates from the data client.
Included details clarifying that <client> is resolved via
NamedDataClient.Name() (e.g., kubernetes or inline), and that data
clients not implementing the NamedDataClient interface report as
unknown (e.g., routes.load_all.unknown).
Related Issues
Multiarch Docker image
Multiarch Docker image is available in GitHub's docker registry:
docker run -it ghcr.io/zalando/skipper:v0.27.51 skipper --help
