You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/11/16 17:12:02 UTC
[jira] [Commented] (BEAM-10909) Grafana posts-commit dashboard
improvements
[ https://issues.apache.org/jira/browse/BEAM-10909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232931#comment-17232931 ]
Beam JIRA Bot commented on BEAM-10909:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.
> Grafana posts-commit dashboard improvements
> -------------------------------------------
>
> Key: BEAM-10909
> URL: https://issues.apache.org/jira/browse/BEAM-10909
> Project: Beam
> Issue Type: Improvement
> Components: testing
> Reporter: Tyson Hamilton
> Priority: P2
> Labels: stale-P2
>
> The post-commit dashboards are an excellent tool for monitoring the health of the project. There are however drawbacks currently that make it less than ideal. This issue represents the master-task, or objective, that groups together a list of subtasks.
> [Post-commit Status dashboard|http://metrics.beam.apache.org/d/8N6LVeCmk/post-commits-status-dashboard?orgId=1]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)