Cloudability How to Optimize Cloudability Performance
For system down issues, navigate to the Outage section in this document
Dashboard & Reports Best Practices
A successful dashboard or widget for Cloudability depends on following best practices, such as selecting the right metrics, creating easy-to-understand visualizations, and optimizing data loading and refresh times. Reviewing factors such as the number of widgets used per dashboard, dashboard sharing and permission settings, and report/chat configuration can help improve performance. Regularly monitoring and fine-tuning these aspects can help ensure the dashboards and widgets continue to perform optimally. See Performance - Dashboard & Widgets Best Practices .
Outage Definitions
Mass Outage: A production incident is a customer impacting event that causes disruption to or a reduction in the quality of a service which requires an engineering response. A production incident can vary widely in severity, ranging from an entire global web service crashing to a small number of users having intermittent errors. An outage is an event where an application is down or unavailable and fully inaccessible (user can't login).
Mass Outage Process: For mass outages, visit status.cloudability.com for the most recent outage activity.
If you are experiencing an outage that is not related to a mass outage, submit a support case with the following information
- Is your issue related to Outage / Work Stoppage
- Have you reviewed the Cloudability Status Page?
- Is one person impacted or multiple users are impacted?
- Is this on a specific page or all pages/dashboards/reports?
The Apptio support team can also investigate specific slowdowns in your environment with the help of HAR files. To learn how to collect a HAR file, visit Apptio Community page.