2019-10-21 - Triage report for "group::apm"
Hi, @dhershkovitch @mnohr @adriel
This is a group or stage level triage package that aims to summarize the feature proposals and bugs which have not been scheduled or triaged. For more information please refer to the handbook:
Scheduling the workload is a collaborative effort by the Product Managers and Engineering Managers for that group. Please work together to provide a best estimate on priority and milestone assignments. For each issue please:
- Determine if the issue should be closed if it is no longer relevant or a duplicate.
- If it is still relevant please assign either a best estimate versioned milestone, the %Backlog or the %Awaiting further demand milestone.
- Specifically for ~bug, if there is no priority or clarity on a versioned milestone, please add a Priority label. Priority labels have an estimate SLO attached to them and help team members and the wider community understand roughly when it will be considered to be scheduled.
- Once a milestone has been assigned please check off the box for that issue.
- Please work with your team to complete the list by the due date set.
feature (non-customer)
Unscheduled-
#34080 (closed) Allow user to report abuse from tracing page warning message Category:Tracing, devopsmonitor, feature, frontend, groupapm -
#33835 (closed) Use updated endpoint for getting aggregated logs Category:Logging, devopsmonitor, feature, frontend, groupapm -
#33834 (closed) Support getting all logs from logs endpoint Category:Logging, backend, devopsmonitor, feature, groupapm -
#33833 (closed) Setup an elasticsearch client to query indexes from rails Category:Logging, backend, devopsmonitor, feature, groupapm -
#33618 (moved) Disable Grafana Update Check & Usage Reporting devopsmonitor, feature, groupapm -
#33555 (closed) Log explorer: Advance search and filters Category:Logging, devopsmonitor, feature, groupapm -
#33551 (closed) Log explorer : compact, display for viewing and analyzing real-time and historic log data. Category:Logging, devopsmonitor, feature, groupapm -
#33017 (closed) Allow large number of environments to be displayed in Environments dropdown Category:Logging, Enterprise Edition, GitLab Ultimate, UI polish, ~"UX ready", backend, devopsmonitor, direction, feature, frontend, groupapm -
#31604 (closed) Request to move custom/additional metrics to CE devopsmonitor, feature, groupapm
Bug Section
For the following bugs. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone and ensure that a priority label is set.
Heatmap for all bugs
Bugs for their priority and severity label are counted here. Every bug should have severity and priority labels applied. Please take a look at the bugs which fall into the columns indicating that the priority or severity labels are currently missing.
~S1 | ~S2 | ~S3 | ~S4 | ~"No severity" | |
---|---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 | 0 |
~P2 | 1 | 5 | 2 | 0 | 0 |
~P3 | 0 | 1 | 26 | 1 | 0 |
~P4 | 0 | 0 | 1 | 14 | 0 |
~"No priority" | 0 | 0 | 0 | 1 | 5 |
frontend ~bug (non-customer)
Unscheduled-
#34168 (closed) More options icon is misaligned in monitor dashboard ~"bug", devopsmonitor, frontend, groupapm, regression, regression:12.3 -
#33760 (closed) Negative values on TimeSeries makes deployments data float in the middle of the chart APM, Deliverable, Enterprise Edition, GitLab Ultimate, ~"UX ready", ~"bug", designreadyforeng, devopsmonitor, frontend, groupapm -
#33254 (confidential) ~"(confidential)"
customer
Unscheduled ~bug with-
#33903 (closed) Dashboard line-chart don't redraw correctly after enabling/disabling metrics ~"S4", ~"bug", customer, devopsmonitor, groupapm, ~"metrics"
Unscheduled ~bug (non-customer)
-
#34021 (closed) Environments dropdown only shows 20 environments ~"P2", ~"S2", ~"bug", devopsmonitor, groupapm -
#33761 (closed) Prometheus Integration page does not detect instance clusters ~"bug", devopsmonitor, groupapm -
#33304 (closed) GitLab deployed Ingress does not collect any metrics ~"bug", devopsmonitor, groupapm, ~"kubernetes" -
#32577 (confidential) ~"(confidential)" -
#32405 (closed) How to understand the ruby-prof result which the sum of sub-process time occupied more than 100% ~"P3", ~"S3", backend, ~"bug", devopsmonitor, groupapm
Heatmap for ~missed-SLO bugs
~S1 | ~S2 | ~S3 | ~S4 | |
---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 |
~P2 | 1 | 1 | 1 | 0 |
~P3 | 0 | 0 | 0 | 0 |
~P4 | 0 | 0 | 0 | 0 |
This is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook: