Yes, Phoenix's disk usage monitor triggers notifications and blocking actions based on real-time threshold checks, not on a fixed cron schedule. The monitor daemon periodically checks current database usage and sends warning emails or blocks writes when configured thresholds are crossed, as described in the <https://arize.com/docs/phoenix/release-notes/07.2025/07.07.2025-databse-disk-usage-monitor|release notes> and <https://github.com/Arize-ai/phoenix/blob/main/docs/section-release-notes/07.2025/07.07.2025-databse-disk-usage-monitor.md|implementation details>.
If disk usage values in notifications remain unchanged over multiple days, this is unexpected and may indicate an issue with the usage calculation or database state. The monitor is designed to recalculate usage on each interval, so values should reflect actual changes in storage consumption (<https://github.com/Arize-ai/phoenix/blob/main/src/phoenix/server/daemons/db_disk_usage_monitor.py|source>). Would you like more detail on troubleshooting or the calculation logic?
Sources:
- <https://github.com/Arize-ai/phoenix/blob/main/docs/section-release-notes/07.2025/07.07.2025-databse-disk-usage-monitor.md|Release notes (GitHub)>
- <https://github.com/Arize-ai/phoenix/blob/main/src/phoenix/server/daemons/db_disk_usage_monitor.py|db_disk_usage_monitor.py>
- <https://arize.com/docs/phoenix/release-notes/07.2025/07.07.2025-databse-disk-usage-monitor|release notes>