is microsoft.sql/services/databases connection_failed a heartbeat-based metric?

Nina Reynolds 1 Reputation point Microsoft Employee
2021-02-23T02:33:42.597+00:00

I saw a connection_failed metric for an Azure SQL Database trigger with no service impact or failures reported in the consuming service.

is connection_failed event (only triggers if a user's connection fails) based, or heartbeat (any TCP failure from a polling service in azure monitor) based?

If it's a heartbeat, does azure monitor itself failing at the poll count as a connection error?

Azure Monitor
Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
3,656 questions
Azure SQL Database
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. KalyanChanumolu-MSFT 8,351 Reputation points
    2021-02-23T04:51:44.85+00:00

    @Nina Reynolds Thank you for reaching out.

    connection_failed is a platform metric. It is the Total number of Failed connections irrespective of the origin.
    The consuming service could be implementing a re-try logic for handling transient connection failures.

    You may want to troubleshoot further if you are seeing a high number of connection failures.
    There is a limit on the maximum number of concurrent connections per SKU, beyond this limit further connections are denied and may result in failures.

    We have a detailed blog post to help you troubleshoot further.

    ----------

    If an answer is helpful, please "Accept answer" or "Up-Vote" for the same which might be beneficial to other community members reading this thread.

    1 person found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.