You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 28, 2021. It is now read-only.
Had a few ideas for ext.science, and thought it would be good to share them here.
Feel free to jot down your opinions on such or your own ideas in the comments of the issue.
Replay events for testing
I had a few ideas such as being able to replay events using decorators or having a method to artificially feed events into the bot without causing side effects, to be able to reproduce bugs and to test if a procedure is working as intended.
Prometheus integration
There was a suggestion to add Prometheus support, to be able to manipulate the data stored easily.
Methods usable by the client
It would be good to have usable statistical methods to be able to easily format information for e.g. an info command.
Some ideas include counters for events received overall (links into Prometheus?), HTTP statistics, most used endpoints, HTTP status counts, and being able to determine which endpoints hit the rate limit bucket the most often.
Had a few ideas for ext.science, and thought it would be good to share them here.
Feel free to jot down your opinions on such or your own ideas in the comments of the issue.
Replay events for testing
I had a few ideas such as being able to replay events using decorators or having a method to artificially feed events into the bot without causing side effects, to be able to reproduce bugs and to test if a procedure is working as intended.
Prometheus integration
There was a suggestion to add Prometheus support, to be able to manipulate the data stored easily.
Methods usable by the client
It would be good to have usable statistical methods to be able to easily format information for e.g. an info command.
Some ideas include counters for events received overall (links into Prometheus?), HTTP statistics, most used endpoints, HTTP status counts, and being able to determine which endpoints hit the rate limit bucket the most often.