PostLogs

What does this project provide

• A REST API for receiving structured log events
• Telegram notification delivery via python-telegram-bot
• MariaDB storage for persisted logs, user sessions, and permissions
• A web admin UI for viewing logs, managing categories, users, and permissions
• Session-based authentication for admin access and API key protection for the log endpoint
• Log records view with export support
• Category configuration management
• Superadmin-only user, project access, and permission management
• Toggle-able Telegram notification settings per category

What was the project before the Big Update

It was a bare bones wrapper of the python-telegram-bot API and whilst a good feature to include in some projects that I wanted it didn't make my life easier in implementing it. Reuse of the API Token and the Group ID was okay with me but finding libraries to support the way I wanted to use the API was hard, especially since I wanted to use it between ecosystems. That was about a month ago, since then I have slowly but surely bit by bit built this platform that needs just a post request to work.

What it has become now

Now the project has become a dashboard that allows not only per user project permission but more fine tuned permissions regarding Editing, Viewing, Exporting and Deleting log contents. It also allows better filtering experience than the initial version. Another favorite feature of mine that the admin can define the log levels for which a message should be sent when they are received.

There are a few small details that make the design feel more polished like:

• The user management interface
• The disabling of users
• The variable access on projects
• Log propagation to other dedicated or not servers and that's not all of them.

It is lacking some vital functionality though, stuff like:

• changing passwords
• changing emails and stuff I haven't figured out yet but will be coming to future releases.

It also has some bugs, stuff like:

• After editing a user you need to insert their password again or else it will not save it's settings
• After editing a user their password can become over-written
• Permissions show as objects due to relationships not being defined correctly but they will be solved in future releases too.

Overall, it has been a fun and quite useful as a project and I do plan to maintain it since not only does it help me but it has potential as a simple and open source (MIT License) log management service.

Thanks for reading! The project can be found in my Codeberg Profile or in the following link!