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
As of now, there are no statistics or logging of the usage of DrawBot.
This is extremely inconvenient as those stats are pretty useful in the development of the bot.
A nice solution, in my opinion, would be maybe a Grafana dashboard, stored in either a grafana db or something like Redis.
This should log command usage stats, as well as CPU/memory loads throughout the day and maybe some other things.
The text was updated successfully, but these errors were encountered:
We should try to consolidate deployment as much as possible. drawbot is ridiculously simple; in general, I don't think its worth adding ancillary services that the end user doesn't directly see a benefit from.
Realistically the most I can see us adding for drawbots current scope is PG. We'll need a database at some point, whether it is SQLite or a full DBMS, and I would not underestimate what can be done with PG alone.
Stats would be perfectly fine to log with a DBMS, and there are likely plenty of existing tools we can use to generate visualizations; even something as simple as dumping a CSV to drop into google sheets / JSON.
So I'll leave it to you to decide whatever the frontend for this is, but as far as data collection itself goes, that's my two cents - do whatever gives us the most value up & down the stack.
As of now, there are no statistics or logging of the usage of DrawBot.
This is extremely inconvenient as those stats are pretty useful in the development of the bot.
A nice solution, in my opinion, would be maybe a Grafana dashboard, stored in either a grafana db or something like Redis.
This should log command usage stats, as well as CPU/memory loads throughout the day and maybe some other things.
The text was updated successfully, but these errors were encountered: