Health check indicates status of user-facing AI features
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Currently, Duo Health Check feedback is centred on connectivity, setup steps, and troubleshooting guidance. However, the overarching job-to-be-done is to help users understand that their AI feature(s) of interest is appropriately configured and functional.
Vision
This issue proposes we extend the Health Check to include information about the status of user-facing Duo features.
- If everything is working, we can provide general positive feedback at the "add-on level", ie, "All Duo
[Pro/Enterprise]features are working as expected" - If specific features are not working, we can offer specific feedback (ie, "Chat seems to not be working", even though everything else is fine).
User Pain Point
This proposal would provide improved feedback to customers in cases where a third-party service is down or degraded.
It provides additional granularity to our MVC healthcheck: We go from "check for things that apply to all of Duo" to "check for things on a feature-by-feature basis".
Related Efforts
To achieve this outcome, we would need to:
- Establish end-to-end status checks from GitLab instance all the way through to third-parties
- Note: there is no specification on whether we execute these checks real-time, or whether GitLab Inc. serves as an intermediary caching layer for pinging third-parties.
- Map third-party service providers to user-facing features
- This mapping will likely change and evolve over time as we identify the best models for each use case.
- Account for "fallback functionality" between different 3P providers
- For example, if a particular provider goes down, and GitLab has a fallback to a secondary provider, service may be functional, albeit degraded.