| title | description | author | ms.author | ms.service | ms.topic | ms.date |
|---|---|---|---|---|---|---|
Azure Advisor for MariaDB |
Learn about Azure Advisor recommendations for MariaDB. |
alau-ms |
alau |
mariadb |
conceptual |
04/12/2021 |
Learn about how Azure Advisor is applied to Azure Database for MariaDB and get answers to common questions.
The Azure Advisor system uses telemetry to issue performance and reliability recommendations for your MariaDB database.
Some recommendations are common to multiple product offerings, while other recommendations are based on product-specific optimizations.
Recommendations are available from the Overview navigation sidebar in the Azure portal. A preview will appear as a banner notification, and details can be viewed in the Notifications section located just below the resource usage graphs.
:::image type="content" source="./media/concepts-azure-advisor-recommendations/advisor-example.png" alt-text="Screenshot of the Azure portal showing an Azure Advisor recommendation.":::
Azure Database for MariaDB prioritize the following types of recommendations:
- Performance: To improve the speed of your MariaDB server. This includes CPU usage, memory pressure, disk utilization, and product-specific server parameters. For more information, see Advisor Performance recommendations.
- Reliability: To ensure and improve the continuity of your business-critical databases. This includes storage limit and connection limit recommendations. For more information, see Advisor Reliability recommendations.
- Cost: To optimize and reduce your overall Azure spending. This includes server right-sizing recommendations. For more information, see Advisor Cost recommendations.
- Daily schedule: For Azure MariaDB databases, we check server telemetry and issue recommendations on a daily schedule. If you make a change to your server configuration, existing recommendations will remain visible until we re-examine telemetry on the following day.
- Performance history: Some of our recommendations are based on performance history. These recommendations will only appear after a server has been operating with the same configuration for 7 days. This allows us to detect patterns of heavy usage (e.g. high CPU activity or high connection volume) over a sustained time period. If you provision a new server or change to a new vCore configuration, these recommendations will be paused temporarily. This prevents legacy telemetry from triggering recommendations on a newly reconfigured server. However, this also means that performance history-based recommendations may not be identified immediately.
For more information, see Azure Advisor Overview.