This guide teaches you how to monitor application health and leverage platform-level metrics to monitor application performance.
Skills Checklist:
Any strategy for the development of new Appian applications must include prioritizing Appian platform health as a foundational element. Effective platform health management is critical to reducing downtime, maintaining high development quality and proactively identifying potential risks that threaten future performance or functionality.
However, in the rush to roll out new apps the (relatively inglorious) work of platform health management is deprioritized, and therefore, maintenance debt accumulates. Furthermore, siloed teams and the traditional communication divide between business partners and IT teams often lead to, at best, a partial or fragmented understanding of platform health. This can introduce unnecessary risks not only for existing projects, but also for future endeavors.
By establishing a structured methodology to run, analyze, and take action on the health of the Appian Platform, you will improve visibility and awareness into the status of your environment and applications, and decrease the likelihood of production issues. Monitoring critical applications, plugins and servers associated with the Appian platform will also help mitigate enterprise-wide risks. Furthermore, regularly upgrading the Appian platform ensures your organization is able to leverage latest product improvements and stay in product compliance to receive support for defects or security fixes.
In order to avoid a fragmented approach to platform health management, Appian strongly recommends using the out-of-the-box Health Check utility on each of your environments; production and non-production (eg. dev, test, and production). Health Check can be run to provide transparency into application design, usage, and risks across your entire Appian program. This utility can be scheduled to automatically collect the information it needs and perform the analysis, so developers maintain focus on high value work. Running Health Check in all environments reduces the risk of quality issues being moved into production in the first place. For example, if you run Health Check in dev at the end of a sprint, you should prevent issues from getting to test, and if you run it in test, you should help prevent things going into production.
Users can explore the Health Check analysis findings via MyAppian. Ideally, the findings should be reviewed on a regular basis by the Platform Owner and Technical Lead for each application on the platform. Since organizations often have multiple applications owned by different teams, it is important that each of these applications has someone reviewing the Health Check output for issues related to their apps. Detailed findings are organized into four areas of your environment: Design, User Experience, Infrastructure and Configuration.
Key Benefits to Health Check
When exploring the Health Check findings, users can filter and sort by various attributes like risk level or category. Historical trends and other environment-level information is also provided to get a good picture of the overall environment health. In addition to the dynamic analysis capability in My Appian, the Health Check utility also generates an Excel report that contains more information. For additional help and details about these reports, check out our Understanding the Health Check Report page.
This is one of the most frequently asked questions regarding Health Check. Appian recommends scheduling Health Check to automatically run at the the intervals listed below:
Allocate 10% of every sprint toward maintenance and backlog work (about 2 hours per full time developer). This ensures that developers have adequate time to research and fix Health Check issues as needed or address other maintenance related activities. If done consistently, this practice will help manage technical debt and enable teams to spend fewer full sprints fixing behind the scenes problems.
For any technology platform, there are key benefits that an organization expects to realize which can be measured to demonstrate value. Well defined metrics will enable the platform owner to not only demonstrate value to the leadership but also establish trust with the business and other stakeholders so the organization can scale its use of the Appian platform effectively.
The program-level metrics can enable the Platform Owner to demonstrate that the platform is being used effectively and providing value to its stakeholders. Appian recommends that platform owners review these metrics monthly and provide summaries to relevant stakeholders or management team members. Some of these metrics can be easily monitored on the Appian platform using MyAppian including:
However, platform level metrics may not be sufficient when there are multiple applications built on the Appian platform for various business units. Application-level metrics specific to a project or a program will enable the platform owner to demonstrate value to the business stakeholders that their investment is giving them valuable returns. These metrics will vary depending on the type of application and the expected benefits. Also, they need to be measured and tracked for each application. Some examples of application-level metrics that might be included on a custom dashboard are:
MyAppian displays a wide variety of metrics pertaining to the health of your platform. Navigate to the Health tab to view information specific to managing and monitoring your Appian environments. Once in the Health tab, select Analyze, and choose an Appian environment. View recent Health Check findings and sort these findings by category, status, risk level, and Application Name in order to get a holistic picture of platform health, and to identify and mitigate risks proactively. To enable the Appian Health Check, simply visit your administrator console in the desired environment.