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

Alert on Wins not landed #330

Open
4 of 9 tasks
snadrus opened this issue Nov 21, 2024 · 0 comments
Open
4 of 9 tasks

Alert on Wins not landed #330

snadrus opened this issue Nov 21, 2024 · 0 comments
Assignees

Comments

@snadrus
Copy link
Contributor

snadrus commented Nov 21, 2024

Checklist

  • This is not a new feature or an enhancement to the Filecoin protocol. If it is, please open an FIP issue.
  • This is not brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on the Curio forum and select the category as Ideas.
  • I have a specific, actionable, and well motivated feature request to propose.

Curio component

  • PoRep Pipeline
  • Snap Deals
  • Market
  • IPNI provider
  • Curio UI
  • Other

What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.

Filfox wins (for some customers) show less that Curio UI displayed wins.
Deep-diving, it's the difference between wins offered & wins landed. That difference is money lost by the SP, so this should be a warning.

Describe the solution you'd like

A curio UI and/or alert to indicate that wins are not landing. This data is available on the existing table as included which can be null if it hasn't been polled yet.

Describe alternatives you've considered

This took Mongo's sharp eye to notice, so not all SPs will be so lucky. It's a high-level health check that could indicate anything from a Curio or Lotus bug to SP configuration or load.

Additional context

No response

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

No branches or pull requests

2 participants