Platform Health Management

Why It’s Important

Any strategy for the development of new Appian applications must include enhancing Appian platform health as a foundational element. The primary benefits of platform health management are reducing downtime, maintaining high development quality and proactively identifying potential risks that threaten future performance. 

However, many organizations struggle to attain a holistic view of platform health as there are numerous, complex facets which comprise any given Appian environment. 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.

Appian Recommendations

By establishing a structured methodology to run, analyze, and take action on the Appian Platform, you will improve visibility and awareness into the health of your environment and applications, and decrease the likelihood of production issues. Monitoring critical applications and servers associated with the Appian platform will also help manage and mitigate enterprise-wide risks.

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 (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. 

Users can explore the Health Check analysis findings via MyAppian. Ideally, the findings should be reviewed monthly by the Platform Owner and Technical Lead for each application that is 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

  • Reduce overall risk
  • Flag best practice design violations
  • Reduce unplanned outages
  • Identify developer skill gaps
  • Identify high priorities for investment


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.

How Frequently Should I Run Health Check?

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:

  • At least once a month in production as part of server and application monitoring.
  • At least once at the end of each sprint as part of a project implementation checklist.
  • After any testing as part of a pre-deployment checklist.

BulbPractitioner Tip: Reserve Time In Every Sprint For Maintenance and Backlog Activities

Allocate 5% of every sprint toward maintenance and backlog work (about 2 hours per full time developer). This ensures that developers have adequate time to fix Health Check issues 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.

Resources

Previous Next
Related
Recommended