At present, we have access to various metrics that are supported in Confluence, as outlined in https://confluence.atlassian.com/doc/app-metrics-reference-1115674758.html. These metrics include a comprehensive list provided by the app monitoring agent, which supplements any JMX beans that the application makes available.

To enhance our insights and monitoring capabilities, it would be extremely beneficial to incorporate additional metrics. Specifically, I suggest the following:

• User Login and Logout Events: Tracking the timestamps and frequency of user logins and logouts would provide valuable data regarding user engagement and activity patterns within the platform.

• Request Duration: Measuring the duration of requests made by users will help us identify performance bottlenecks and optimize system responsiveness.

• Common Statistics: Gathering detailed information on various aspects of the application, including:
    - Attachments: Total storage used and the number of attachments available.
    - Pages: The total number of pages created within the system.
    - Blog Posts: The count of blog posts published and their engagement metrics.
    - Global Spaces: The number of global spaces created for collaboration across teams.
    - Personal Spaces: The number of personal spaces assigned to individual users for private use.

• User Statistics: It’s important to track various user-related metrics, such as:
    - Allowed Users: The total number of users authorized to access the system.
    - Active Users: The number of users actively engaging with the application within a specific timeframe.
    - {}Sessions: Detailed tracking of user sessions, including the number of five-hour sessions as well as the number of sessions initiated today.
• License Usage Metrics

Incorporating these additional metrics would greatly improve our ability to monitor user activity, performance, and overall application health.