Application and Server Monitoring

Now that you’ve built and released your application on the Appian platform, it’s important to utilize Appian’s monitoring features to their full potential. You should leverage Appian logs errors and performance metrics that can be used to identify application or server problems that would otherwise go unreported by users.

Process Alerts

During the execution of a process, an alert will be sent to the process administrators when an error or exception occurs. An alert contains the error and a link to the process that errored. There are a number of reasons an alert may be sent, commonly they are caused by:

  • External services such as a database or web service temporarily being unavailable. This can be corrected by restarting the failed node once the service is available again.
  • Users do not have access rights to complete operation. This can be solved by adding the user to the right group or updating the security of the object being accessed and restarting the failed node.
  • An application defect that was not identified during testing. The solution will depend on the application, but can usually be solved by modifying a process variable to the correct value or by using in-flight modification if process changes are required.

Monitoring Rule Performance

The rule performance monitoring is helpful for identifying application bottlenecks. Sort the table by highest average time and highest number of executions to find the most valuable expressions to optimize. For example an expression that is used often (large number of executions) and also slow (high average response time) is very valuable to optimize. An expression with high executions and medium response times is more valuable to optimize than an expression with low executions and high response times as it’s used much more often.

Monitoring Logs

Appian’s logs are very useful for identifying errors that occur outside of processes such as an error with a record view or task form. One of the most important logs for monitoring an application is the design errors log which captures every expression error that directly impacted an end user. These types of errors often stop a user from completing their work so are important to identify and address quickly.

On single application server hosts the Log Reader plug-in can be used to build processes that monitor the logs. This is useful in places where an in-house tool like Splunk or solarwinds is not available or cannot access the logs directly. Those using cloud can leverage in-house tools for monitoring logs if they’re capable of accessing the logs over the internet via HTTP.

For additional information about how to monitor your Appian servers checkout the Server Monitoring Checklist and Server Diagnostics pages on Community.

Previous Home