Logging

On This Page

Purpose

The Logging page in the Admin Console allows you to configure logging for integrations to facilitate troubleshooting.

Access

To access the Logging page, go to the Admin Console. Then, in the left navigation menu, under Integration, click Logging.

Settings

The Logging page has three sections that control different types of logging:

Trace Logging: Enables trace logs for integrations, web APIs, and platform API requests.
HTTP Request/Response Logging: Captures the raw HTTP request and response messages for integrations and web APIs.
AI Input/Output Logging: Records the inputs and outputs of AI model executions for auditing and monitoring.

/admin-logging

Trace Logging

Trace logging captures performance and diagnostic data for integrations, web APIs, and platform API requests.

Select one or more of the following options to start writing trace data to the corresponding log files:

Integration trace logging: Writes to the integration_trace.csv log.
Web API trace logging: Writes to the web_api_trace.csv log.
Appian Platform API trace logging: Writes to the appian_platform_api_trace.csv log.

Tip: The only potentially sensitive data that is captured in the trace log is the username of the user who called the integration.

HTTP Request/Response Logging

HTTP request and response logging capture raw HTTP request and response messages for integrations and web APIs that have logging turned on in their design object.

Note: These logs may contain sensitive data or credentials. Before enabling HTTP request/response logging, review the integration logging guidelines and web API logging guidelines.

Select one or more of the following options to start writing HTTP request and response data to the corresponding log files:

HTTP request/response logging for integrations: Writes to integration_req_resp_activity.log. You can enable logging for any integration object that uses an HTTP or OpenAPI connected system.
HTTP request/response logging for web APIs: Writes to web_api_req_resp_activity.log. You can enable logging for any web API object.

AI Input/Output Logging

AI input/output logging helps you monitor and audit AI usage within your Appian environment.

Note: The input/output logs may contain sensitive data or credentials. Before enabling input/ouput logging, it's important to understand the AI input/output logging safeguards.

Select Enable input/output logging under AI Input/Output Logging to start writing to ai_input_output_activity.log.

Logging safeguards

There are a number of safeguards in place to ensure that AI input/output logging doesn't store sensitive data when used correctly:

Administrator-only access: The APPIAN_HOME/logs/perflogs/ai_input_output_activity.log log is only accessible by system administrators. This prevents any privilege escalations for developers who shouldn't be able to see certain integrations.
Log rollover policy: The log files roll over based on time and size. No AI input/output log will ever last more than 7 days. The cumulative size of all rollover over AI input/output logs will never exceed 100 MB. To learn more about the log rollover policy, see the Managing Log Files.

Avoid enabling input/output logging if:

Inputs or outputs include sensitive information (for example, PII or credentials) without proper safeguards.
The data is not necessary for auditing or monitoring purposes.

Feedback

Was this page helpful?