Introduction

Confluence is a team collaboration software from Atlassian, using which you can create, organize, and discuss work with your team. It enables project collaboration, eases information creation, maintenance, and dissemination, and thus helps your teams work better. For instance, with the help of Confluence, you can create pages using which you can add/import and manage content, email these pages to share content with your team, and even notify team members by email whenever content changes.

If say, such emails are not delivered in time, Project teams will not be able to take key decisions, promptly; this can significantly impact user productivity. Likewise, if users are unable to search a page and locate information they need quickly, user experience with Confluence is bound to suffer. Besides the above, since Confluence is a Java- based software, issues in the underlying JVM can also adversely affect the overall performance of Confluence. To avoid this, administrators should continuously monitor the availability, responsiveness, and operational health of Atlassian Confluence.

eG Enterprise provides a 100% web-based monitoring model for Atlassian Confluence. Each layer of this model is mapped to tests that monitor the email activity of Confluence, its searching and indexing operation, and its interactions with the database. In the process, these tests proactively alert administrators to email delivery bottlenecks, latencies in searching and indexing, and connection failures with the eG database, thus enabling administrators to take quick action against current / potential anomalies. Additionally, since Confluence is a Java-based application, this model also reports critical statistics pertaining to the health of the JVM in which Confluence runs; this way, resource contentions and abnormal thread activity at the JVM-level are brought to light. Moreover, you can, if required, configure eG's Java Business Transaction Monitor (BTM) to track every transaction to Confluence. The eG Java BTM is capable of tracing the path of a transaction, measuring overall transaction responsiveness and the time taken at each point cut, and alerting administrators to slow transactions and the root-cause of the slowness.