### Problem We do not have standard way of asking for information from customers to better understand the state of their environment asit related to Cloud Connector. Whilst we are making steps to improve this, it would be useful to have a script that we have on hand that can be run by us or by the support team to help speed up diagnosing problems. ### Proposal - Create a script and work with support engineering to support customers who are running older Gitlab versions. (< 17.4). - Create a rake task that would utilize existing Health Check probes. ## `This rails script` * Saved as a [snippet](https://gitlab.com/gitlab-org/gitlab/-/snippets/3734617 "cloud connector health check") * Can be downloaded and used by customers running older instances to troubleshoot DUO. ## `The rake task:` - `cloud_connector:health_check` * deployed with the monolith, customers running the latest version ( %"17.4") could run the rake task out of the box. * It will use existing Health Check probes, which will be extended to provide more detailed information. * Easier to maintain, and extend in time, as we will introduce more probes in the future. ### Documentation When complete, this should be documented in the following places: * ~"group::cloud connector"'s request for help template. This will ensure we get a dump of relevant data for any escalated support requests. * https://docs.gitlab.com/ee/user/gitlab_duo/turn_on_off.html#troubleshooting