Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

Feature ID: PF-85
Status: 📋 Specification
Spec Reference: PF-85-automation-observability-dashboard.md
Last Updated: 2026-03-16

​
Overview

PF-85 provides a unified automation observability surface by aggregating metrics from workflow executions, dead letter queue, SLA runtime state, and business process health. It integrates with PF-10 notifications for threshold alerts and links users into existing detail views in FW-22, FW-47, PF-82, and PF-83.

​
Integration Points (from Spec)

DependencyTypePurpose
PF-82 (Business Process Registry)Data / InboundRead pf_business_processes health metrics and drill-down to process registry
PF-83 (SLA Management Platform Layer)Data / InboundRead pf_sla_instances compliance metrics and drill-down to SLA view
PF-36 (System Health Dashboard)Platform / OutboundOptional embed of observability summary widget
PF-10 (Notifications)Platform / OutboundSend threshold breach notifications
FW-22 (Execution Monitoring)Data + NavigationRead execution metrics and navigate to execution detail views
FW-47 (Dead Letter Queue)Data + NavigationRead DLQ metrics and navigate to DLQ admin

​
API / Platform Contracts

  • DB view (planned): pf_automation_observability_current
    • Current-point and rolling-window counters scoped by organization.
  • DB function (planned): pf_get_automation_timeseries(p_organization_id, p_window, p_core_filter)
    • Returns bucketed trend metrics for charts.
  • Frontend hooks (planned):
    • useObservabilityCurrent()
    • useObservabilityTimeseries()
    • useAlertThresholds()
  • Settings contract (existing table): fw_module_settings
    • Module automation_observability, keys for alert thresholds and UI defaults.

​
Scheduled Processing Contract

  • Phase 1: threshold evaluation runs as part of PF-36 health-check cycle.
  • Phase 2 (deferred): dedicated pg_cron + edge function alert checker.
  • Notification path: PF-10 notification delivery with cooldown semantics to avoid alert fatigue.

​
Event Contracts

PF-85 does not introduce new event names in Phase 1. It consumes persisted state and emits notifications through existing PF-10 pathways.

​
Security and Tenant Isolation

  • All metrics are organization-scoped; no cross-tenant aggregation.
  • Timeseries access enforces org access via fw_has_org_access() in a SECURITY DEFINER function.
  • UI access is permission-gated:
    • platform.automation.observability.view
    • platform.automation.observability.manage
  • Dashboard content is aggregate operational telemetry only (no PHI/PII payload display).