Repository navigation
Connector creation - improve error messaging from server #54386
Description
Activity
Pinging @elastic/kibana-alerting-services (Team:Alerting Services)
Moving from
7.12 - Candidatesto7.x - Candidates.Moving from
7.x - Candidatesto8.x - Candidates (Backlog)after the latest 7.x planning session.The messages from config-schema can get overly wordy. We're really in need of a better solution for JS data validation, as config-schema is only intended for validating Kibana config values into TS-typed objects. It has a number of downsides including the types generated are read-only, so can't be reused for cases where we want construct data of the same shape to pass somewhere else (eg, tests). It also can cause issues if the validated objects are re-validated - durations turn into objects which when passed through the same validation again will fail.
I don't think there's much use in trying to "fix" anything here - except perhaps extremely annoying messages that we see frequently - since we really need to replace what we're using. For those extremely annoying messages, we can provide custom validate methods which produce nicer messages than config-schema does.
Leaving this open though, as I suspect we may get questions about the error messages in the future, and can point them here.
Closing as no longer relevant.
(Review feedback from docs team on the connectors UI)
#48959 adds a connector creation flyout where you fill a form, and submitting it calls the create action API. We display server-side validation errors, but the messaging is not always clear.
Here are two specific examples:
Example 1: webhook
Example 2: email
Is there a way to make these messages easier to read/understand to the user? Both are very
verbose, and the problem is not made clear.
xpack.actions.whitelistedHostsdocumentation about the whitelisting setting (this page)?All the error messages should start with capital E - "Error validating..."