You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Scott Wegner (JIRA)" <ji...@apache.org> on 2019/01/08 17:00:00 UTC
[jira] [Commented] (BEAM-6381) :beam-test-infra-metrics:test
org.apache.beam.testinfra.metrics.ProberTests > CheckGrafanaStalenessAlerts
failed
[ https://issues.apache.org/jira/browse/BEAM-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737299#comment-16737299 ]
Scott Wegner commented on BEAM-6381:
------------------------------------
Investigating now. Notes:
* It appears this was a one-off flake; the [next test run|https://builds.apache.org/job/beam_Release_NightlySnapshot/296/] succeeded.
* The [failure message|https://scans.gradle.com/s/cvp2a2ngeiomg/tests/ewe6rnmgqseim-lmwbktf4d6kh4] is: {{Input data is stale! http://104.154.241.245/d/data-freshness. Expression: (alert.state == ok)}}
* Checking the [freshness dashboard|http://104.154.241.245/d/data-freshness/source-data-freshness?orgId=1] currently shows all ingest feeds healthy; max staleness is GitHub @34 mins.
The test doesn't give much information in terms of what the actual staleness values were at the time; we should improve the log output.
> :beam-test-infra-metrics:test org.apache.beam.testinfra.metrics.ProberTests > CheckGrafanaStalenessAlerts failed
> ----------------------------------------------------------------------------------------------------------------
>
> Key: BEAM-6381
> URL: https://issues.apache.org/jira/browse/BEAM-6381
> Project: Beam
> Issue Type: Test
> Components: test-failures
> Reporter: Boyuan Zhang
> Assignee: Scott Wegner
> Priority: Major
>
> https://builds.apache.org/job/beam_Release_NightlySnapshot/295/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)