Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Diagnosing issues is very difficult becuase there is no audit trail of retries #4828

Open
ramonsmits opened this issue Feb 20, 2025 · 0 comments

Comments

@ramonsmits
Copy link
Member

Describe the suggested improvement

When diagnosting retry issues it is not clear what steps were executed.

The UI indicates that a retry operation was completed but there is no information about when certain steps were executed.

It would be nice if information would be shown like:

yyyy-MM-dd hh:mm:ss [1] Failed
yyyy-MM-dd hh:mm:ss [1] Ingested by ServiceControl
yyyy-MM-dd hh:mm:ss [1] Included in batch XXX
yyyy-MM-dd hh:mm:ss [1] Staged for retry
yyyy-MM-dd hh:mm:ss [1] Dispatched as part of staging
yyyy-MM-dd hh:mm:ss [2] Failed (nth time)
yyyy-MM-dd hh:mm:ss [2] Ingested by ServiceControl
yyyy-MM-dd hh:mm:ss [2] Included in batch XXX
yyyy-MM-dd hh:mm:ss [2] Staged for retry
yyyy-MM-dd hh:mm:ss [2] Dispatched as part of staging
yyyy-MM-dd hh:mm:ss [3] Failed
yyyy-MM-dd hh:mm:ss [3] Archived, will be purged on yyyy-MM-dd hh:mm:ss

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant