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

Alerts #1

Open
pbuda opened this issue Apr 6, 2017 · 0 comments
Open

Alerts #1

pbuda opened this issue Apr 6, 2017 · 0 comments

Comments

@pbuda
Copy link
Owner

pbuda commented Apr 6, 2017

Application should support an alerts engine.

The way I see it is that you can define alert (via slack for now) using command alert (crypto) (price) (relative crypto), for example alert ETH 0.05 BTC.
Backend should determine current price of ETH in BTC and define whether it should trigger the alert when the price rises (current ETH price is lower than defined in alert) or when the price drops (current ETH price is higher than defined in alert).
Once triggered, alert should be removed automatically.
It would be best to only allow one alert per crypto pair/price so probably it would be a good idea to use crypto pair/price as some soft of key (primary key?).

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

1 participant