用于 MySQL 的 Azure 顾问Azure Advisor for MySQL

了解如何将 Azure 顾问应用于 Azure Database for MySQL,并获得常见问题的解答。Learn about how Azure Advisor is applied to Azure Database for MySQL and get answers to common questions.

什么是用于 MySQL 的 Azure 顾问?What is Azure Advisor for MySQL?

Azure 顾问系统使用遥测为 MySQL 数据库发布性能和可靠性建议。The Azure Advisor system uses telemetry to issue performance and reliability recommendations for your MySQL database.

某些建议通用于多种产品/服务,而其他建议基于特定于产品的优化。Some recommendations are common to multiple product offerings, while other recommendations are based on product-specific optimizations.

在哪里可以查看我的建议?Where can I view my recommendations?

可以从 Azure 门户中的“概述”导航边栏中查看建议。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.

显示 Azure 顾问建议的 Azure 门户屏幕截图。

建议类型Recommendation types

Azure Database for MySQL 优先考虑以下类型的建议:Azure Database for MySQL prioritize the following types of recommendations:

  • 性能:提高 MySQL 服务器的运行速度。Performance: To improve the speed of your MySQL server. 其中包括 CPU 使用率、内存压力、连接池、磁盘利用率和特定于产品的服务器参数。This includes CPU usage, memory pressure, connection pooling, 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.
  • 成本:优化并降低 Azure 总支出。Cost: To optimize and reduce your overall Azure spending. 其中包括服务器适当调整大小的建议。This includes server right-sizing recommendations. 有关详细信息,请参阅顾问成本建议For more information, see Advisor Cost recommendations.

了解你的建议Understanding your recommendations

  • 每日计划:对于 Azure MySQL 数据库,我们会检查服务器遥测数据,并按每日计划发布建议。Daily schedule: For Azure MySQL 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. 这些建议只有在服务器以相同配置运行 7 天后才会出现。These recommendations will only appear after a server has been operating with the same configuration for 7 days. 这样一来,我们就可以检测持续的一段时间段内的大量使用情况(例如,高 CPU 活动或高连接量)的模式。This allows us to detect patterns of heavy usage (e.g. high CPU activity or high connection volume) over a sustained time period. 如果你预配新服务器或更改为新的 vCore 配置,这些建议将暂时停止。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.

后续步骤Next steps

有关详细信息,请参阅 Azure 顾问概述For more information, see Azure Advisor Overview.