Errors in calculating the DB Connection Pool, NumActive, NumIdle values in Confluence

XMLWordPrintable

    • 1
    • Severity 3 - Minor

      Issue Summary

      JMX metrics for Confluence include things like Database active connections, Database connection latency, and Database idle connections. The issue is that when reviewing the metrics that are being captured in the atlassian-confluence-ipd-monitoring.log file things don't seem to be correct. The active DB connection metric always seems to report 0 and the idle DB connection metric always seems to report 1. These values never seem to change despite several changes in configuration and statuses.

      The IPD tool allows for system monitoring to proactively address potential issues before they affect productivity. The In-Product Diagnostics feature provides detailed, real-time information about your Confluence environment, aiding in system optimization. The DB.CONNECTION.POOL.NUMACTIVE.VALUE and DB.CONNECTION.POOL.NUMIDLE.VALUE should reflect actual values, but during tests, these values remained static instead of varying as expected.

      This is reproducible on the Data Center: yes

      Steps to Reproduce

      IPD monitoring is enabled by default. To manage it:

      1. Go to Administration  > General Configuration
      2. In the left panel, select Monitoring.
      3. Use the Enable in-product diagnostics toggle to enable or disable IPD monitoring.

      Check the atlassian-confluence-ipd-monitoring.log for Database connectivity, HTTP connection, Indexing, and Infrastructure metrics.

      Expected Results

      Values should reflect the up-to-date status of each component.

      Actual Results

      Several values remain unchanged/static, regardless of their true condition.

      • 2024-02-07 15:56:36,893-0300 IPDMONITORING {"timestamp":"1707332196","label":"DB.CONNECTION.POOL.NUMACTIVE.VALUE","attributes":{"_value":"0.0"}}
        ...
        2024-02-07 15:56:36,893-0300 IPDMONITORING {"timestamp":"1707332196","label":"DB.CONNECTION.POOL.NUMIDLE.VALUE","attributes":{"_value":"1.0"}}

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            minnsey
            Reporter:
            Luís Eduardo de Almeida (Inactive)
            Votes:
            4 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: