Agent skill · data analytics · jeremylongshore
palantir-observability
Design Foundry observability using build metrics, execution history, governed logs, audit exports, and monitoring subscriptions. Use when defining dashboards, alerts, or operational evidence. Trigger with "Foundry observability" or "Palantir monitoring".
Why this skill is useful
Adds executable scripts for structured logging, Prometheus metrics, and alerting specific to Palantir Foundry integrations that enhance observability capabilities.
What it needs
Requires grafana, prometheus installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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. Instructions 1. Define measurable service and data objectives, owners, thresholds, and response actions before creating dashboards. 2. Map each signal to the authoritative Foundry surface and identify its permission, marking, retention, and export requirements. 3. Create views or exports with minimum fields and protected destinations; avoid logging object values, prompts, or secrets. 4. Test each alert with a controlled failure and confirm routing, deduplication, acknowledgement, escalation, and recovery. 5. Review false positives, blind spots, access, retention, and evidence quality after a representative operating window. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/palantir-observability