baseline

To compute a 24-hour Acquia log baseline, download logs across configured environments and aggregate hourly fingerprint velocity into rising, stable, or falling classifications. This establishes a reliable baseline for detecting escalating error patterns and reducing monitoring noise.

Fingerprint velocity baseline computation aggregates hourly error rates from Acquia logs into rising, stable, or falling classifications. By persisting these per-fingerprint counts, downstream triage logic can distinguish genuine escalation anomalies from routine background noise.

Yes, running Acquia log baseline computation requires a local authenticated acli session and valid drover configuration. The Skill performs preflight checks for both before downloading 24-hour logs and updating the baseline persistence file.

Yes, you can filter Acquia error baseline computation to a single environment such as production. The baseline computation supports optional per-environment filtering, allowing you to target specific environments during initial setup or post-deployment recalibration.

You should recalibrate Acquia log baselines immediately after a deployment to capture new error patterns. Recalibration downloads fresh 24-hour logs, recomputes fingerprint velocity, and updates the baseline file to ensure triage logic detects post-deployment anomalies accurately.

The best way to schedule long-window Acquia baseline refresh runs is using the built-in loop-style scheduling mechanism. This automates the 24-hour log download and fingerprint aggregation process, ensuring baseline data stays current for ongoing triage and escalation detection.