Which automated health checks belong in every production Xperience by Kentico implementation?

I’ve been building a structured health scanner into Xperience by Kentico applications so operational problems surface before editors or visitors report them. The useful checks seem to span more than uptime: content delivery, configuration, scheduled processing, external dependencies, and application behavior can all look “up” while part of the experience is degraded.

For teams running Xperience in production, which checks have proven essential? My initial baseline includes website and API reachability and latency; content and media retrieval; failed publishing or background tasks; application errors; search or index freshness; cache behavior; email and integration endpoints; certificate expiration; storage or database thresholds; and configuration drift between environments.

Which checks should be platform-level versus application-specific, and which signals have actually caught real incidents early? I’d also be interested in sensible frequencies and alert thresholds that avoid turning the scanner into noise.

Tags:
SaaS Xperience Administration Environments Test automation

Answers

To response this discussion, you have to login first.