Recommended Approach for Centralized Log Collection for Appian on Kubernetes

We are looking to integrate Appian running on Kubernetes with a centralized logging platform such as OpenSearch or Elasticsearch and would like to understand the recommended and supported architecture.

Our initial assumption was that a Kubernetes DaemonSet-based collector would be sufficient. However, we have observed that many Appian logs are written to files within the pod filesystem rather than to stdout/stderr, making them unavailable through typical Kubernetes container log collection methods.

Given this architecture, we would like guidance on the following:

• What is the recommended and supported approach for collecting Appian logs and forwarding them to OpenSearch or Elasticsearch?
• Does Appian provide a native or supported mechanism to export, stream, or forward logs to an external logging platform?
• If logs are stored on mounted volumes, is it supported to collect those files directly using tools such as Fluent Bit, Fluentd, Filebeat, or similar log shippers?
• Does Appian recommend a sidecar collector pattern, a DaemonSet collector, or another architecture for Kubernetes deployments?
• Are there any supportability concerns or best practices related to accessing Appian log files from mounted volumes for ingestion into external observability platforms?
• Which Appian log types are recommended for centralized collection and operational monitoring?

Our goal is to centralize Appian logs while remaining aligned with Appian-supported deployment and operational practices.