Polycrate API 0.11.17 released: Timeline Chart Debugging

With Polycrate API 0.11.17, we enhance the diagnostic capabilities for the timeline charts in the detail UIs.

The Problem

After the 0.11.16 release, it was observed that the timeline charts in S3 Bucket Detail and LoadBalancer Instance Detail were not displaying data - even though the aggregated values (average, maximum) were correctly calculated.

The Paradox: Both calculations use the same VictoriaMetrics response. _calculate_average_from_metrics() works, but _extract_storage_timeline() returns an empty list.

The Solution

1. Consistent Parsing

The timeline extraction now uses exactly the same syntax as the working average calculation - proven code instead of variation.

2. Error-Tracking

Parse errors are now counted and logged. This allows us to immediately see if and how many values are lost during parsing.

3. Debug Response in Admin

If the timeline is empty but an average value exists, the RAW VictoriaMetrics response is stored in the metrics_data field. In Django Admin, you can check under queries.1h.debug_response_sample to see what data VictoriaMetrics actually provides.

Additional Fixes

• UTC-Timezone: LoadBalancer timeline datetime conversion now explicitly uses UTC for consistency

→ Full Release Notes

After the Update

1. Reconcile S3 Bucket / LoadBalancer (Reconcile Button)
2. Check Django Admin: metrics_data.queries.1h.debug_response_sample
3. Analyze Logs: Search for “Timeline” or “parse errors”

polycrate-api Block

The polycrate-api block has been updated to version 0.5.21:

polycrate pull cargo.ayedo.cloud/ayedo/k8s/polycrate-api
polycrate run polycrate-api install

Polycrate is ayedo’s Infrastructure-as-Code platform for declarative multi-cluster management. Learn more →