Palantir Foundry Observability Design

Overview

Use Foundry-native telemetry for Foundry workloads and export only when there is a governed consumer. Distinguish operational metrics, service/trace logs, execution history, monitoring notifications, and audit logs because they have different access and retention semantics.

Prerequisites

• Identify the resource, owner, service objectives, failure modes, audiences, data classification, and incident process.
• Inventory available build metrics, resource metrics, execution history, logs, monitoring views, audit exports, and external notification targets.
• Read references/official-docs.md and confirm current log-access and marking policy.
• Define the minimum telemetry needed to detect user-visible or data-quality failures.

Current Contract

• Transform build metrics expose CPU, memory, and job behavior in build reports.
• Ontology and AIP metrics, execution history, and logs have different permission requirements; logs may require Edit permission, enabled log access, and markings.
• Organization log exports support Palantir or OpenTelemetry payload formats and must respect source-executor and export-dataset marking requirements.
• Audit logs record high-level security and administrative activity and require tightly controlled export datasets.