Skip to content

[BEAM-5837] Add dashboard for monitoring input data staleness#6820

Merged
swegner merged 5 commits intoapache:masterfrom
swegner:staleness_dashboard
Oct 26, 2018
Merged

[BEAM-5837] Add dashboard for monitoring input data staleness#6820
swegner merged 5 commits intoapache:masterfrom
swegner:staleness_dashboard

Conversation

@swegner
Copy link
Contributor

@swegner swegner commented Oct 24, 2018

This will make it easier to monitor whether we have fresh input data in
in our dashboards. We can set up notifications or probing against the
dahsboard alerts.


Follow this checklist to help us incorporate your contribution quickly and easily:

  • Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.

Post-Commit Tests Status (on master branch)

Lang SDK Apex Dataflow Flink Gearpump Samza Spark
Go Build Status --- --- --- --- --- ---
Java Build Status Build Status Build Status Build Status Build Status Build Status Build Status Build Status
Python Build Status --- Build Status
Build Status
Build Status --- --- ---

@swegner
Copy link
Contributor Author

swegner commented Oct 24, 2018

R: @Ardagan

@swegner swegner force-pushed the staleness_dashboard branch from d7415b5 to ee18f01 Compare October 24, 2018 22:27
@swegner
Copy link
Contributor Author

swegner commented Oct 24, 2018

This will make it easier to monitor whether we have fresh input data in
in our dashboards. We can set up notifications or probing against the
dahsboard alerts.
@swegner swegner force-pushed the staleness_dashboard branch from ee18f01 to da19d3d Compare October 24, 2018 22:29
@swegner
Copy link
Contributor Author

swegner commented Oct 24, 2018

The alert needs to be changed to 8 hours instead of mins

Copy link
Contributor

@Ardagan Ardagan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also dashboard should alert on more than 8 minutes. Even though we run sync scripts every 5 mins, this will change for GHA script.
Also we get timing for Jenkins jobs based on duration, so we can have longer intervals there.

I suggest to set it to 8 hours, this will cover period of jenkins jobs kick off that is 6 hours.

@swegner
Copy link
Contributor Author

swegner commented Oct 25, 2018

Feedback addressed; @Ardagan PTAL

@swegner swegner merged commit 0f9ef7c into apache:master Oct 26, 2018
@swegner swegner deleted the staleness_dashboard branch October 26, 2018 03:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants