Monitor group issues requiring attention
Hi @joshlambert,
Here is a list of feature proposals without a milestone.
We would like to ask you to determine whether this issue should be scheduled or closed. For each issue please:
- Close the issue out if it is no longer relevant or a duplicate.
- Assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.
For the issues triaged please check off the box in front of the given issue.
Please work with your team to complete the list this week.
-
https://gitlab.com/gitlab-org/gitlab-ce/issues/58370 Runbook integration in Incidents ~"Monitor", ~"devops:monitor", ~"feature", ~"incident management" -
https://gitlab.com/gitlab-org/gitlab-ce/issues/58255 Allow alert annotation to select issue template ~"Monitor", depth, ~"devops:monitor", ~"feature", ~"incident management" -
https://gitlab.com/gitlab-org/gitlab-ce/issues/58213 Slack notification for background migration failures ~"Monitor", database, ~"error tracking", ~"feature" -
https://gitlab.com/gitlab-org/gitlab-ce/issues/57802 Test out Loki to see if we should use for our logging solution ~"Monitor", Persona: DevOps Engineer, Persona: Security Analyst, Persona: Software developer, Persona: Systems Administrator, ~"devops:monitor", ~"feature", ~"logging" -
https://gitlab.com/gitlab-org/gitlab-ce/issues/57749 Variable substitution in templates ~"Monitor", Persona: DevOps Engineer, Persona: Development Team Lead, Persona: Product Manager, Persona: Security Analyst, Persona: Software developer, Persona: Systems Administrator, ~"Plan", ~"devops:plan", ~"feature" -
https://gitlab.com/gitlab-org/gitlab-ce/issues/57567 Add an API call that reaches backend to the healthcheck GitLab Self-Monitoring, ~"Monitor", ~"P3", Persona: Software developer, ~"S3", customer, ~"feature" -
https://gitlab.com/gitlab-org/gitlab-ce/issues/57549 Generic alert webhook ~"Monitor", Persona: DevOps Engineer, Persona: Development Team Lead, Persona: Security Analyst, Persona: Software developer, Persona: Systems Administrator, ~"devops:monitor", ~"feature", ~"incident management" -
https://gitlab.com/gitlab-org/gitlab-ce/issues/57379 Prometheus Service Discovery for GitLab HA instances ~"Monitor", Persona: Systems Administrator, ~"devops:monitor", ~"feature" -
https://gitlab.com/gitlab-org/gitlab-ce/issues/57258 (confidential) ~"(confidential)" -
https://gitlab.com/gitlab-org/gitlab-ce/issues/57171 Link to Grafana on metrics dashboard ~"Monitor", Persona: DevOps Engineer, Persona: Software developer, Persona: Systems Administrator, ~"devops:monitor", ~"feature" -
https://gitlab.com/gitlab-org/gitlab-ce/issues/57170 Deploy Sentry to cluster ~"Monitor", Persona: DevOps Engineer, Persona: Development Team Lead, Persona: Software developer, Persona: Systems Administrator, ~"devops:monitor", ~"feature" -
https://gitlab.com/gitlab-org/gitlab-ce/issues/57136 Grafana dashboard importer ~"Monitor", Persona: DevOps Engineer, Persona: Software developer, Persona: Systems Administrator, ~"devops:monitor", ~"feature" -
https://gitlab.com/gitlab-org/gitlab-ce/issues/57135 Load data for charts individually instead of all charts at once ~"Monitor", Persona: DevOps Engineer, Persona: Software developer, Persona: Systems Administrator, ~"devops:monitor", ~"feature", ~"metrics" -
https://gitlab.com/gitlab-org/gitlab-ce/issues/57058 Support multiple manually configured Prometheus servers ~"Monitor", Persona: DevOps Engineer, Persona: Development Team Lead, Persona: Software developer, Persona: Systems Administrator, ~"devops:monitor", ~"feature" -
https://gitlab.com/gitlab-org/gitlab-ce/issues/56882 Automatic query step adjustment ~"Monitor", Persona: DevOps Engineer, Persona: Software developer, ~"devops:monitor", ~"feature"
Hi @ClemMakesApps,
Here is a list of frontend bugs without severity and priority for the team.
We would like to ask you to work with your team to triage the issues in this list. For each issue please:
- Close the issue if it is no longer relevant or a duplicate.
- Assign a Priority and a Severity Label.
- Assign either a versioned milestone or to the %Backlog milestone.
The definition of these labels are defined at:
- Priority Labels (~P1 / ~P2 / ~P3 / ~P4)
- Severity Labels (~S1 / ~S2 / ~S3 / ~S4)
For the issues triaged please check off the box in front of the given issue.
Please work with your team to complete the list this week.
Hi @sengelhard,
Here is a list of bugs without severity and priority for the team.
We would like to ask you to work with your team to triage the issues in this list. For each issue please:
- Close the issue if it is no longer relevant or a duplicate.
- Assign a Priority and a Severity Label.
- Assign either a versioned milestone or to the %Backlog milestone.
The definition of these labels are defined at:
- Priority Labels (~P1 / ~P2 / ~P3 / ~P4)
- Severity Labels (~S1 / ~S2 / ~S3 / ~S4)
For the issues triaged please check off the box in front of the given issue.
Please work with your team to complete the list this week.
-
https://gitlab.com/gitlab-org/gitlab-ce/issues/58573 whitelist network or ip in gitlab.yml without token return 404 ~"Monitor", ~"bug", ~"devops:monitor" -
https://gitlab.com/gitlab-org/gitlab-ce/issues/49615 health check via whitelist_ip not working according to docs ~"Monitor", ~"bug", ~"devops:monitor"
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: