BUG: Mismatched keys in Ombi Webhook Status Endpoint #30

Closed
opened 2026-05-22 15:39:53 +01:00 by Gandalf · 1 comment
Owner

The Ombi Webhook status handler attempts to read metrics.eventCount and metrics.lastEventTimestamp. However, the cache utility writes metrics.eventsReceived and metrics.lastWebhookTimestamp. This mismatch leaves statistics showing 0/null in the admin UI. Integration tests mocked wrong keys, masking this issue.

The Ombi Webhook status handler attempts to read metrics.eventCount and metrics.lastEventTimestamp. However, the cache utility writes metrics.eventsReceived and metrics.lastWebhookTimestamp. This mismatch leaves statistics showing 0/null in the admin UI. Integration tests mocked wrong keys, masking this issue.
Gandalf added the Kind/Bug label 2026-05-22 15:41:03 +01:00
Author
Owner

Resolution: Corrected server/routes/ombi.js to read eventsReceived (from metrics.eventsReceived) and lastWebhookTimestamp (from metrics.lastWebhookTimestamp) to match the properties stored by the cache. Aligned the mock cache response OMBI_WEBHOOK_METRICS in tests/integration/ombi.test.js to match the correct keys.

Resolution: Corrected server/routes/ombi.js to read eventsReceived (from metrics.eventsReceived) and lastWebhookTimestamp (from metrics.lastWebhookTimestamp) to match the properties stored by the cache. Aligned the mock cache response OMBI_WEBHOOK_METRICS in tests/integration/ombi.test.js to match the correct keys.
Gandalf added the Area/Proxy label 2026-05-28 11:53:58 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Gandalf/sofarr#30