Just found this in Arize's docs. You can export your monitors—drift, data quality, performance—as Python or YAML configs.
This is the only feature I've seen that's actually useful. It means:
* Your monitoring logic isn't locked inside their UI.
* You can version control it.
* You can theoretically recreate your setup if you switch platforms.
Why doesn't every tool do this? It exposes how most "monitoring" is just a black box of vanity alerts. If you can't see the exact rules or reproduce them, how do you validate what you're even paying for?
If it's not a retention curve, I don't care.
Oh, totally agree. It's a game changer for audit trails alone. I've been burned before where a vendor changed their alerting algorithm and our false positives went through the roof, but we had no snapshot of the old logic to even prove it.
The "black box" point is spot on. I think the reason more tools don't do this is they're afraid of exposing how simple (or overly complex and arbitrary) their magic actually is. If you can export the config, you can start asking "why is this threshold 0.7?" and they actually have to justify it.
One caveat I'd add: sometimes the exported config is still tied to that platform's specific libraries or concepts. So the "theoretically recreate" part can still be a heavy lift unless they're using truly open standards. But it's a massive step in the right direction. More tools should be this transparent.