Smart API Monitoring - JSON expressions#1620

Problem:
When having a more sophisticated API health endpoints that can actually return more then just as single ‘ok’ response the status calculation based on a single JSON response is very limiting. Currently, the API monitoring only allows to check for a specific property value, but that’s all.

Proposal:
Instead, having a custom expression available / override would be more than welcome. This would allow custom status evaluation with latency as a fallback for more complex API endpoints.

Use case:
Health endpoint can return a degraded, down, up, unknown or even more customized properties. The new feature for monitor settings would add a customized expression for JSON responses to decide what the actual status will be, while also significantly increasing precision, reliability and false alarms. Service can return 200 but still be degraded. The actual threshold for unsuccessful attempts or slow response would remain as a classic fallback.