Skip to content

feat(monitoring): add stuck fiat outputs metric to payment observer#3876

Merged
davidleomay merged 1 commit into
developfrom
feat/monitoring-stuck-fiat-outputs
Jun 12, 2026
Merged

feat(monitoring): add stuck fiat outputs metric to payment observer#3876
davidleomay merged 1 commit into
developfrom
feat/monitoring-stuck-fiat-outputs

Conversation

@davidleomay

Copy link
Copy Markdown
Member

Summary

Fiat outputs that fail transmission to the bank (e.g. Olkypay model validation errors like CLIENT_INVALID_ZIPCODE) sit ready but untransmitted indefinitely — the error is only visible in the entity info column, with no monitoring alert.

  • New stuckFiatOutputs metric in the payment observer: counts fiat outputs with isReadyDate older than 1 hour, no isTransmittedDate, and isComplete = false
  • Surfaced in the health check as a DEGRADED issue (N stuck fiat outputs)
  • FiatOutputRepository registered in RepositoryFactory

Test plan

  • npm run type-check
  • npx eslint on changed files
  • Verify metric appears in monitoring data after deploy (e.g. fiat output 81359 scenario)

Fiat outputs can fail transmission to the bank (e.g. Olkypay model
validation errors) and then sit ready but untransmitted indefinitely,
visible only in the entity info column. Count outputs with isReadyDate
older than one hour and no isTransmittedDate in the payment observer
and surface them in the health check.
@davidleomay davidleomay merged commit f43b6b3 into develop Jun 12, 2026
7 checks passed
@davidleomay davidleomay deleted the feat/monitoring-stuck-fiat-outputs branch June 12, 2026 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant