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 an user having someone else host the bot for me I don't have access to the CLI logs of the bot and therefore cannot see which errors occurred when adding new rules or executing commands with unexpected results.
In order to improve this the bot should have an interface any authorized user can use to see the bot logs. To make this possible the logging (>= info level) should be written into a table with a sane default retention (30d?) and auto-cleanup of that table. An interface should be available to query information from that table.
This also would make the log actor way more useful as the logs can be seen without access to the server itself.
The text was updated successfully, but these errors were encountered:
In order to improve this the bot should have an interface any authorized user can use to see the bot logs. To make this possible the logging (>= info level) should be written into a table with a sane default retention (30d?) and auto-cleanup of that table. An interface should be available to query information from that table.
This also would make the
log
actor way more useful as the logs can be seen without access to the server itself.The text was updated successfully, but these errors were encountered: