What’s New At Releem - February 2025

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.

You can now analyze trends over periods of up to three months. This gives you a broader view of your server’s performance over time.

Added Query Analytics Date Range Filter
Your query analytics now adjust based on the selected period. Just choose a timeframe from the dropdown, and view the queries executed during that period (Feature request #318).

Automated Query Analytics Collection
We’ve removed the “Load Data” button and added a date range field to your Query Analytics. SQL Query Analytics now automatically collects updated data, which simplifies your workflow.

New Query Truncation Status Health Check
Truncated queries can lead to incomplete data, which might skew your performance insights and analytics. But you can identify and address these queries quickly with our newest health check. Learn more.

CSV Export for Query Analytics
You can now export your query analytics data to CSV for further analysis, team discussions, reporting, or debugging. It’s your data, leverage it however you need (Feature request #384).

Added Recommendation Thresholds
We’ve introduced a threshold for how significant configuration changes need to be to trigger recommendations. This way, you aren’t getting bothered with a bunch of small changes (like a 20KB buffer change) (Feature request #188)

Added Percona XtraDB Cluster Support
Releem now recognizes Percona XtraDB Cluster environments, delivering recommendations specifically optimized for your cluster configuration.

Added Duplicate Server Check
The duplicate server check now prevents mixing metrics from servers with the same hostname. This keeps your data accurate and reliable.

Improved Releem Expert System
We wanted to reduce the risk of incorrect recommendations due to inconsistencies in MySQL variables. Releem Platform now validates MySQL configurations for consistency before making any recommendations.

Improved Query Analysis
- Indexed Column Functions
Releem now recognizes when you're applying functions to indexed columns and offers smarter indexing recommendations based on the specific condition used
- Column Comparison Conditions
We've fine-tuned our analysis to better detect comparisons between columns within the same table so you can quickly address any indexing issue

Latency Calculation Fix
We’ve resolved an issue skewing some latency calculations. Previously, queries not executed in the prior interval were excluded from storage, leaving no baseline for comparison and causing occasional inaccuracies. Now, by storing all queries consistently, your latency metrics are precise and reliable (Issue #391)

Cache Hit Rate Fix
We've fixed a bug where the health check "Table Definition Cache Hit Rate" would unexpectedly drop to 0%. The problem stemmed from how platform calculated the "Open Table Definitions" over a one-day period – if MySQL opened all table definitions, the metric could erroneously report zero, affecting the cache hit rate (Issue #390)

AWS RDS Recommendation Improvements
Previously, our recommendation for the maximum table_open_cache value didn't fully account for the open_files_limit setting on AWS RDS instances. We’ve resolved this issue to provide more accurate guidance for your RDS instance. (Issue #389)