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

+# Metrics (Dashboards) – Features list
+
+Descriptions of features that we will present to the respondents.
+
+## Guidelines
+ 
+- Clear and sufficiently detailed description that sets the feature into 
+necessary system context.
+- Simple language without GitLab lingo or sales pitching
+
+### Feature description structure
+- Feature: What can the user see in the UI
+- Behavior: What does it do
+- Value: Why do we want to introduce it
+
+### Questions
+In the survey the questions about feature will be asked in a following way: 
+
+- Rearrange panels using drag and drop
+- How would you feel if you had this feature?
+     - I like it
+     - I expect it
+     - I am neutral
+     - I can tolerate it
+     - I dislike it
+- How would you feel if you did not have this feature?
+     - I like it
+     - I expect it
+     - I am neutral
+     - I can tolerate it
+     - I dislike it
+
+## Current features
+- GitLab monitoring is... Consists of dashboards.
+- Dashboard consists of a number of panels. Each panel can contain a static 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.
+
+## 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.
+
+##### ⭐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. 
+It will allow you to have smaller number of dashboards created and therefore 
+make dashboard management easier. 
+
+<img src='./image_5.png' width=600px />
+
+##### ⭐Out of the box dashboard for monitoring different technologies and services
+A set of out-of-the-box dashboards for the most common technologies and services
+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
+<!--??-->
+This will improve organization of your dashboards.  
+
+##### ⭐Add tags to dashboard for easier search
+Tag with searchable keywords
+that you can assign to dashboards.
+It will allow you to find dashboards faster.
+
+##### ⭐Add a special panel with custom hyperlinks
+A special panel with a list of custom hyperlinks
+so you can drill down to a tool of your choice (e.g. another dashboard or external tool)
+right from the dashboard UI.
+To speed up navigation between different tools.
+
+<img src='./image_1.png' width=600px /> 
+
+##### ⭐Rearange panels using drag and drop
+A possibility
+to rearrange panels using drag and drop rather than by editing the yaml file. 
+
+<img src='./image.png' width=600px />
+
+##### ⭐Resize panels with cursor 
+A possibility
+to resize panels using cursor rather than by editing the yaml file.
+
+### Panel level
+
+##### ⭐Add custom hyperlinks to the options menu of a panel
+Custom hyperlink in the options menu of a panel,
+so you can drill down to a tool of your choice (e.g. another dashboard or external tool)
+right from the relevant panel.
+To speed up navigation between different tools.
+
+<img src='./image_2.png' width=600px />
+
+##### ⭐Annotate metric charts
+<img src='./image_3.png' width=600px />
+
+Annotation, a vertical line in a chart, that shows custom message on hover,
+so you can manually highlight an important point within the chart.
+To improve collaboration and informativeness of the chart.
+
+##### ⭐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.
+
+##### ⭐Add thresholds that do not trigger alerts
+
+<img src='./image_4.png' width=600px />
+
+Current experience: Thresholds and alerts are tightly coupled
+Feature: Allow the users to set and see diffrent thresholds without triggering an alert
+
+##### ⭐Change the appearance of the line on a chart (color, width, dotted line, etc..)
+
+##### ⭐Ability to correlate between metric chart and logs