Health Check Data FAQ

This page explains the types of data that are collected by Health Check and how Appian stores and uses this data.

Health Check collects environment data through a three-step process:

• Step 1: Data collection
• Step 2: Data review
• Step 3: Data analysis.

This page covers the data collection step. To learn how the full process works, see How Health Check works. To view the summarized findings and analysis, use the Analyze option on the Health tab in MyAppian.

Collected data

Health Check collects two categories of information from your environment: system logs and metadata about your design objects. The following sections describe what Health Check collects and how you can review it before analysis.

What data does Health Check collect?

Health Check collects system logs and object information to provide you with meaningful feedback about your applications' design patterns and performance risks. During data collection, the logs collected include, but are not limited to:

• Audit.
• Data metrics.
• Performance.
• Troubleshooting (including application server).

During data collection, a series of Health Check-specific logs are also generated and collected. These logs primarily contain information about applications and their objects.

The types of data that Health Check can collect in log files may include, but are not limited to:

• Design object properties, including:
  • Name.
  • Description.
  • Security.
  • Visibility expressions.
  • URLs and URL stubs.
• Usernames.
• User agents.
• Integration details.
  • Systems being integrated with.
  • Frequency of integration calls.
  • Endpoints
• Error messages (which may include user-entered data).
  • Design errors.
  • K error logs.
• Server details, including hostnames, IP addresses, etc.

How can I review collected Health Check data?

System administrators are responsible for reviewing the generated ZIP file during the data review step of their Health Check runs. During data review, system administrators have the option to download and review the data collection ZIP file that Health Check has generated before the ZIP file is uploaded to Appian Community for analysis. Any files that system administrators do not want to share with Appian can be removed from the ZIP file during this step, and they can then optionally upload a new version of the ZIP file for analysis. Appian will use the ZIP file that has been submitted during data review to generate your Health Check report.

System administrators can opt to autoapprove the data review step during Health Check runs. Enabling this option will skip over the data review step during Health Checks and directly upload the data collection ZIP file to Appian Community for analysis. Learn more about how to enable autoapproval.

Data storage and retention

Appian stores several artifacts from each Health Check run and retains them for defined periods. The following sections describe what Appian stores, where the data is stored, and how long it is kept.

What data does Appian store?

For each Health Check run, Appian stores metadata about the run, a copy of the data collection ZIP file (including the raw log files), and a copy of the generated Health Check report.

Where is the data stored?

All customer Health Check data is stored in Appian Cloud's Northern Virginia region and is subject to the same security controls as all production Appian Cloud environments.

How long is the data stored?

For production environments, data collection ZIP files are retained for three months after the date of the Health Check run. For non-production environments, Appian retains only the latest ZIP file for up to three months.

The metadata from the Health Check analysis is stored for three months for both production and non-production environments.

Health Check findings are stored and available for up to one year.

Data access and use

Access to Health Check data is limited to specific Appian teams, and Appian uses the data for defined purposes. The following sections describe who can access the data, how Appian uses it, and how to request its removal.

Who at Appian has access to the data?

Data collection ZIP files are only accessible by Customer Success Architects, members of Appian Support, CS Accelerate, and Cloud Engineering.

Health Check reports and run metadata are available for general use within Appian. This includes the Engineering, Customer Success, and other departments.

Is the data shared with third parties?

Appian does not share any Health Check data externally with third parties. However, Appian may share a customer's Health Check analysis data with contractors previously approved to work on projects for that specific customer.

How does Appian use the data?

The data is used for several purposes within Appian including, but not limited to:

• To generate Health Check analysis for customers.
• To evaluate customer environment health.
• To aggregate Health Check metadata across customers and analyze usage and adoption.
• To inform business decisions and improve our product.

Can I have my data removed?

If you would like Appian to remove your Health Check data, contact Appian Support.

Feedback