Commit 1c99a992 authored by Jerome Ng's avatar Jerome Ng

Add implementation status file changes

parent 24ec265e
......@@ -72,15 +72,14 @@
<% end %>
<% if performance_indicator.instrumentation %>
<b>Instrumentation: <%= color_code_instrumentation(performance_indicator.instrumentation.level) %></b>
<% if performance_indicator.implementation %>
<b>Implmentation Status:</b> <%= performance_indicator.implementation.status %>
<% performance_indicator.instrumentation.reasons.each do |reason| %>
<% performance_indicator.implementation.reasons.each do |reason| %>
<%=" * #{reason}"%>
<% end %>
<% end %>
<% if performance_indicator.lessons %>
<b>Lessons Learned (<%= Date::MONTHNAMES[Date.today.prev_month.month] %>):</b>
......
......@@ -8,10 +8,6 @@
<%= partial 'includes/performance_indicator_health' %>
### Instrumentation
<%= partial 'includes/performance_indicator_instrumentation' %>
## How to work with pages like this
<figure class="video_container">
......@@ -70,8 +66,7 @@ Each - denotes a dictionary of values for a new (K)PI. The current elements (or
| `pi_type` | Optional | indicates the [Product PI type](https://about.gitlab.com/handbook/product/performance-indicators/#structure) (Ex: AMAU, GMAU, SMAU) |
| `product_analytics_type` | Optional | indicates if the metric is available on SaaS, SM (self-managed), or Both. |
| `is_primary` | Optional | boolean flag that indicates if this is the Primary PI for the Product Group. |
| `instrumentation` | Optional | has two additional elements/property - level (inclusive value between 0-3) and reasons. This should be updated monthly before Key Meetings by the DRI. |
| `implementation_status` | Optional | indicates the [Product Analytics Workflow](https://about.gitlab.com/handbook/product/performance-indicators/#product-analytics-workflow) status |
| `implementation` | Optional | indicates the [Product Analytics Workflow](https://about.gitlab.com/handbook/product/performance-indicators/#product-analytics-workflow) status and reasons. This should be updated monthly before Key Meetings by the DRI. |
### Guidelines
......@@ -92,4 +87,4 @@ Each - denotes a dictionary of values for a new (K)PI. The current elements (or
- Add the `shared_dashboard`, `chart` , and the `dashboard` key-value pairs to the [corresponding Performance Indicators data file](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/performance_indicators/) under the `sisense_data` property
* Avoid `:` in strings as it's an important character in YAML and will confuse the data parsing process. Put the string in "quotes" if you really need to use a `:`
* `urls:` should be an array (indented lines starting with dashes) even if you only have one url
* Both `maturity.level` and `health.level` display a value between 0 and 3 (inclusive).
* `health.level` displays a value between 0 and 3 (inclusive).
| Value | Level | Meaning |
|-------|-------|---------|
| 3 | <%= color_code_instrumentation(3) %> | We are correctly capturing and measuring data for GitLab.com and self-managed instances. |
| 2 | <%= color_code_instrumentation(2) %> | Missing one of: GitLab.com or self-managed data. |
| 1 | <%= color_code_instrumentation(1) %> | Missing both: GitLab.com and self-managed data. |
| 0 | <%= color_code_instrumentation(0) %> | Unknown |
......@@ -50,7 +50,11 @@ The section PI overview shows Primary PIs for each Product Section, Stage, and G
<td><a href="#<%= kpi.name.gsub("/",'').gsub(/[!@%&"()$%^*,:;.]/, '').gsub(" ","-").downcase %>"><%= name_parts[2]%></a></td>
<td><%= color_code_health kpi.health.level %></td>
<td><%= kpi.product_analytics_type %></td>
<td><%= kpi.implementation_status %></td>
<td>
<% if kpi.implementation %>
<%= kpi.implementation.status %>
<% end %>
</td>
</tr>
<% end %>
<% end %>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment