Another month wrapped up at Releem, and this month we focused on removing friction in everyday workflows.
We finally brought Dark Mode to Releem Dashboard 🎉 It took longer than expected, with small UI details needing clean up before it was ready to ship. We quietly rolled the feature out, but a few dozen users enabled it right away!
We also shipped Dashboard Sharing 💪 This was something we initially treated as a lower-priority request, but it kept coming up. Eventually it became clear it was blocking teams from using Releem together, so we moved it up and shipped it.
Community Contributions
We're always collecting issues and feature requests on our GitHub. Here's where you can contribute:
Issues – If you encounter any problems or bugs, report them here.
Feature Requests – Have an idea to make Releem even better? Share your suggestions here.
Updates to Releem Dashboard
We’ve shipped a set of dashboard improvements focused on usability, collaboration, and the workflows you use everyday:
- Dashboard Sharing & User Roles
You can now invite users to shared dashboards per server through server Settings and assign roles (Issue #279):
- Viewer – Read-only access to dashboard and insights
- Editor – Can change settings and apply recommendations.
- Dark Mode
You can now apply a dark theme to the dashboard. Dark Mode has always had a dedicated group of users who overwhelmingly prefer it to light mode. We’re glad to finally make it available.
- Export Process List to CSV
You can now export the process list directly to CSV, making it easier to analyze queries, share snapshots, and include data in reports and incident reviews (Issue #437).
- Improved Apply Workflow
To reduce confusion during configuration changes, the Apply button has been moved directly into the Recommended Configuration popup. This keeps review and action in one place.
Updates to Releem Platform
Several fixes this month focused on recommendation accuracy and schema analysis:
- Smarter Buffer Pool Recommendations
Releem now takes overall system memory pressure into account when generating innodb_buffer_pool_size recommendations. When RAM usage is already high, recommended values are scaled down instead of being calculated solely from total available memory. This prevents over-allocation in constrained environments and reduces the risk of memory pressure (Issue #481).
- Primary Key Detection Fix
Resolved an issue where tables could be flagged as missing a primary key where the Agent has limited schema permissions. Previously, missing column-level metadata could lead to false “no primary key” warnings. The updated logic now handles these cases correctly (Issue #475).
Updates to Releem Agent
- Expanded Initial Configuration Options
We added support for generating an initial MySQL configuration directly from the Releem Agent. With a single command, the agent analyzes server hardware and creates a sensible baseline config for new or default MySQL installations, before workload-based tuning kicks in. You can find full details in the updated documentation.
Top comments (0)