darkbot 0.3
since forumlancer bot is broken, I added its features to darkbot now.
funny enough, you can thank @Groshyr again for kicking me to do that.
new feature:
You can track appearance of new forum messages.
It underwent a major refactorization and now reimplemented in golang with clean architecture for code scalability to add new features
general stability added, because all errors are now handled way better with Golang approach that handles most of them at compile time.
project saves ready for deployment docker images at docker hub
darkbot has its own server now only for itself
# Features
Adding player bases for tracking in discord channel
# Project status
in active development until at least all planned features are added from the list "Comin soon" and "For later"
May have some issues which will be resolved as soon as possible
May went through database wipes during deployments of new releases. Announcement about new releases will be made into Discord channel where it joined and here.
# Future plans: Comming Soon
Adding players for tracking based on tag in nickname or star systems / regions to track
Adding configurable alert triggers to base and player tracking
# Future plans: For later
Adding forum post for tracking
# Future plans: For more later
Adding resource tracking at player bases
Adding some useful help scripts to calculate analytics
Reported issue:
Unexpected high CPU and disk writing takes place at some point of time. Taking up to 100% of resources, including high disk resource writing
Leading at some point to auto reboot of kube cluster
Status:
2023-01-25: Temporal solution #1 for autorecovery during this problem is ensured to be. Application will autorelaunch on its own during if problem will happen again
2023-01-25: Temporal solution #2 is found. Added limit to running POD in terms of CPU, which will force its automated restart if it goes above the limit. It will ensure automated restart within healthy parameters of a server
2023-01-26: 24 hours passed without repeated incident in CPU peaks, monitoring for few days more.
2023-01-29: Source reason is identified: in 1 hour RAM storage is overfilled with scrapped data, which leads to using disk swap, which causes intensive desk reading/writing, which leads to cluster death and reboot.
2023-01-29: Source reason is fixed in #19
2023-01-29: Awaiting deployment 2023-01-30: deployed as v0.1.1. issues is solved. Monitoring results
Excellent progress @darkwind --- This is awesome!
Keep up the good work and thanks for all the efforts
I am looking forward to seeing a better fancy layout/format for the POBs information by the bot.