Details
-
Bug
-
Status: Resolved
-
P2
-
Resolution: Fixed
-
None
-
None
Description
A failure gradle run from my local machine: https://gradle.com/s/sqcwi7bo3a2nw. Stacktrace:
org.apache.beam.testinfra.metrics.ProberTests > CheckGrafanaStalenessAlerts FAILED
java.lang.AssertionError: Input data is stale! [id:1, dashboardId:5, dashboardUid:data-freshness, dashboardSlug:source-data-freshness, panelId:2, name:Source Data Freshness alert, state:alerting, newStateDate:2019-07-30T02:55:02Z, evalDate:0001-01-01T00:00:00Z, evalData:[evalMatches:[[metric:GitHub, tags:null, value:482.16617045000004]]], executionError:, url:/d/data-freshness/source-data-freshness]
See: http://104.154.241.245/d/data-freshness. Expression: (alert.state == ok)
at org.codehaus.groovy.runtime.InvokerHelper.assertFailed(InvokerHelper.java:406)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.assertFailed(ScriptBytecodeAdapter.java:650)
...
From the stacktrace suggestion, I went to http://104.154.241.245/d/data-freshness and got Github source is older than a week, which I guess is potentially the failure reason. However, no further instruction on what to do next.
After some investigations, I found this test `:beam-test-infra-metrics:test` is added to beam_Prober_CommunityMetrics but never got passed (either failed or skipped due to cache).
Is there anything wrong with Github data refresh? Should we reevaluate the alert on dashboard or modify the test?
Attachments
Issue Links
- links to
