This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Is there an alarm for excessive connections in Foglight for SQL Server?

SQL has ~32K limit on connections.  Is there a built-in alarm that monitors the number of connections to a database instance?

Parents
  • Hello Randy,

    we have a dashboard where you see the amount of current sessions (active and inactive). I checked the current rules and there are some rules which are firing when we see a baseline deviation. For example the rule "DBSS - All Active Connections Baseline Deviation" is firing when we see a deviation from the baseline of active connections. The baseline is being caculated by Foglight and based on the amount of active connections in the past.

    I cannot find a rule firing based on a static amount of connections. But you can create your own rule as the metric you need is available. There is a collection called "SQL Server Connection Summary" and it collects a lot of connection related metrics:

    Active Connections Percent, All Active Connections, Background Sessions, Blocked Connections, Blockers Connections, Connections Running DBCC, Foreground Sessions, Internal Connections, Machine Connections, Max Block Time, Max Connections Allowed, Max Threads Allowed, SQL Active Threads, SQL Executions, System Connections, Total Connections, User Active Connections, User Connections, User Inactive Connections, Worker Threads Used Percent

    Does that help?

    Regards
    Nicola
Reply
  • Hello Randy,

    we have a dashboard where you see the amount of current sessions (active and inactive). I checked the current rules and there are some rules which are firing when we see a baseline deviation. For example the rule "DBSS - All Active Connections Baseline Deviation" is firing when we see a deviation from the baseline of active connections. The baseline is being caculated by Foglight and based on the amount of active connections in the past.

    I cannot find a rule firing based on a static amount of connections. But you can create your own rule as the metric you need is available. There is a collection called "SQL Server Connection Summary" and it collects a lot of connection related metrics:

    Active Connections Percent, All Active Connections, Background Sessions, Blocked Connections, Blockers Connections, Connections Running DBCC, Foreground Sessions, Internal Connections, Machine Connections, Max Block Time, Max Connections Allowed, Max Threads Allowed, SQL Active Threads, SQL Executions, System Connections, Total Connections, User Active Connections, User Connections, User Inactive Connections, Worker Threads Used Percent

    Does that help?

    Regards
    Nicola
Children
No Data