hub

Data Platform

Core Governance

dashboardSummaryhubLineageverified_userGovernancemonitoringPerformancenotificationsAlerts1securityWatchdog
AU

Admin User

Enterprise Core

monitor_heart

Governance & SLAs

NiFi Ecosystem • Enterprise Platform • Mock Data

calendar_todayDemo · Last 30 Days
Production Status: Live
verified
Sync StatusUp to date

Monitored Processes

dataset

...

Mock pipelines

Outlier Days Excluded

warning

0

Simulated samples

Operating Mode

verified_user

Demo

Simulated data

Last Updated

update

...

Sample snapshot

SLA Calculation Methodology & Statistical Learning Engine

How baseline performance targets and adaptive anomaly thresholds are modeled across pipelines

Stage 01

System Outlier Pruning

Evaluates 180-day telemetry. If a calendar day suffers a daily success rate < 50% (threshold = 0.50), it is tagged as an infrastructure/network crash and removed via an Anti-Join.

AntiJoin(df, daily_rate < 0.50)
Stage 02

Temporal Sessionization

Partitions executions into 2-hour sliding buckets (hour // 2) to collapse retry storms into unified operational sessions with normalized diurnal start seconds.

session = group_by(proceso, date, h//2)
Stage 03

Median Multiplier Filter

Computes the median duration (median_duration_s). Any hanging, zombie, or stuck sessions exceeding 300% (3×) of the median are purged from the quantile baseline.

duration_s ≤ median * 3.0
Stage 04

Adaptive SLA Buffer

Extracts the 95th Percentile (P95) and adds an adaptive cushion of 15% (min 30 min) to set the critical operational SLA threshold.

SLA = P95 + max(P95 * 0.15, 1800s)
Mathematical Formulation:Expected end time is modeled as T_expected = AvgStartTime + AvgDuration; Maximum SLA cutoff is T_max = AvgStartTime + SLA_Duration with automatic day-shift offsets (+1d).
Executed by: calculate_baselines.py & learn_behavior.py
Loading SLAs...