Health Check

Hi ​@ariannad4431,

Yes. I use Appian Health Check through the Admin Console as part of monitoring and maintaining application health, especially before major releases or when investigating performance issues. It helps identify potential issues such as inefficient process models, query performance problems, object complexity, design best practice violations, and overall application health metrics.

I find it useful because it provides actionable recommendations and helps proactively improve performance, scalability, and maintainability. However, I don't rely on it alone. I combine Health Check findings with application logs, Performance View, process analytics, database analysis, and real-world user feedback to diagnose and resolve issues.

It suits my needs for identifying performance bottlenecks, design issues, and governance recommendations. I use it as a diagnostic and optimization tool, while complementing it with other monitoring and troubleshooting methods for complete root-cause analysis.

you would aghere for a self-serve tool, without the need for administrator permissions, with more granular analysis at the single object level (interface, rule, process model)

It’s not perfect and probably needs updating but I still use it.

I still use it. It is great for identifying certain types of problems, but it has some limitations and there are better ways to get a picture of overall environment health:

• Some of the high-importance issues it identifies are symptoms rather than the root cause, but they are a good starting point
• Designer > Monitoring > Process Model Metrics tab gives better information about the memory usage and archival strategies for the top memory using PM’s
• Designer > Monitoring > Query Performance gives much better information about tracking down non-performing queries for the data fabric
• There are hidden tabs in the health check that are still great for giving information about non-performant database views
• The design-errors log usually gives better details and context about what users are experiencing, and the the time periods of the day in which they experience them. This can help you track down any processes that cause resource contention on the system by correlating timestamps (e.g. large database computations that cause a brief surge in query timeouts).
• Actual CPU / memory / heap / load metrics / request volume are great for understanding spikes in performance issues as they relate to time. These can be found on the Appian Support portal, but I think there’s also a log file that can be pulled for some of the metrics.
• If your system has a lot of integrations, I’ve found that the logs around integrations & web apis (the details, not the summaries) give a much better understanding about what is happening with the integrations, including response times and any burst volumes.