Survey for monitoring feature prioritization

Links

• #882 (closed) Research request
• #883 (closed) Recruitment request
• Project folder with Research plan, Survey and Features list
• Survey
  • Version 1 (Please input Test into the Job title field if you don't want us to analyze your answer)
• Analysis spreadsheets
  • Internal – GitLab SREs
  • External – Firstlook
• Dovetail project

Checklist

Design survey

• Draft the survey
• Create a list of features
• Transfer the survey questions to Qualtrics @akiripolsky

Pilot survey

• Fill the survey and fix any problematic pieces in the MR
• Fix the survey in Qualtrics @akiripolsky @nadia_sotnikova

Collect responses – Round 1 – Internal

• Distribute the survey to GitLab SRE team @dhershkovitch
• Improve the questionnaire based on the feedback from SREs @akiripolsky
• Input the data collected to the analysis spreadsheet @akiripolsky

Collect responses – Round 2 – External

• Open a Recruiting request issue. Assign it to the relevant Research Coordinator @dhershkovitch
• When the survey is ready, ask Emily in the recruitment issue to send the survey to external participants from FirstLook @akiripolsky
• Notify Research Coordinator of survey closure. @akiripolsky

Document findings

• Analyze the data @akiripolsky
• Document the results @dhershkovitch
• Document insights in Dovetail
• Create actionable insight issue
• Update Metrics direction page
• Update the Problem validation research issue. Link to findings in Dovetail. Unmark as confidential if applicable. Close issue.

Survey about requirements for monitoring/Features list.md

@@ -6,6 +6,7 @@ Descriptions of features that we will present to the respondents.
 - Clear and sufficiently detailed description that sets the feature into 
 necessary system context.
 - Simple language without GitLab lingo or sales pitching
+- Describe proper features, not MVCs. 
 
 ### Feature description structure
 - Feature: What can the user see in the UI
@@ -31,25 +32,27 @@ In the survey the questions about feature will be asked in a following way:
 
 ## Current features
 - GitLab monitoring is... Consists of dashboards.
-- Dashboard consists of a number of panels. Each panel can contain a static a chart, 
+- Dashboard consists of a number of panels. Each panel can contain a chart, 
 a numerical indicator or a static markdown text. It is possible to create new 
 and delete existing dashboards. 
-- Configuration of each dashboard is done by editing a yaml file.
+- Configuration of each dashboard is done by editing its configuration yaml file.
+- Alerts that are set on a metric are visualized on the metric chart. 
 
 ## New features
 
 ### Dashboard level
 
 ##### ⭐Import dashboard templates to create new dashboards
-Dashboard creation templates
-that you can choose from when creating new dashboards.
-It will speed up the dashboard creation process and improve consistency.
+Templates for yaml configuration files
+that you can choose when creating new dashboards. 
+Templates contain basic file structure, configuration examples and comments
+to speed up the dashboard creation process and improve consistency across dashboards.
 
 ##### ⭐Add variables to a dashboard
-An special interactive 'quick configuration panel'
-where you can tune specific variables of the dashboard right in the dashboard UI. 
+Interactive 'quick configuration panel'
+where you can select specific variables of the dashboard right in the dashboard UI. 
 It will allow you to have smaller number of dashboards created and therefore 
-make dashboard management easier. 
+make dashboard management simpler. 
 
 <img src='./image_5.png' width=600px />
 
@@ -59,15 +62,13 @@ that are configured automatically when you set up monitoring in GitLab.
 It will improve experience of users that just started using the monitoring 
 features of GitLab. 
 
-##### ⭐Ability to delete out of the box dashboards from Metrics
-
 ##### ⭐Group dashboards into folders
 Dashboard folders in the dropdown 
-that you can group your dashboards with
+that you can group your dashboards in
 to improve organization of your dashboards.  
 
 ##### ⭐Add tags to dashboard for easier search
-Tag with searchable keywords
+Tags with searchable keywords
 that you can assign to dashboards.
 It will allow you to find dashboards faster.
 
@@ -100,18 +101,16 @@ To speed up navigation between different tools.
 <img src='./image_2.png' width=600px />
 
 ##### ⭐Annotate metric charts
-Annotation, a vertical line in a chart, that shows custom message on hover,
-so you can manually highlight an important point within the chart.
+Annotation, a vertical line in a chart that shows custom message on hover,
+so you can highlight an important point within the chart.
 To improve collaboration and informativeness of the chart.
 
 <img src='./image_3.png' width=600px />
 
 ##### ⭐Configure alert directly from a metric chart
 A contextual alert configuration popup openable from within the metric chart
-where you can configure alerts
-without the necessity to navigate to a dedicated alert configuration page.
-It will improve the speed of alert configuration and provide better awareness 
-of the underlying metric.
+where you can configure alerts without the necessity to navigate to a dedicated alert configuration page.
+It will improve the speed of alert configuration and provide better awareness of the underlying metric.
 
 ##### ⭐Add thresholds that do not trigger alerts
 
@@ -122,4 +121,10 @@ Feature: Allow the users to set and see diffrent thresholds without triggering a
 
 ##### ⭐Change the appearance of the line on a chart (color, width, dotted line, etc..)
 
-##### ⭐Ability to correlate between metric chart and logs
+##### ⭐Set a dashboard as Metrics home page for the whole project (admin setting)
+
+An admin or a maintainer of a project can set a dashboard as Metrics home page which will be the default landing page for Metrics for all users.
+
+##### ⭐Override the admin Metrics home page settings with a user-specific Metrics home page setting
+
+Individual users can set the dashboard they use the most as Metrics home page, which will override the default admin setting.
\ No newline at end of file