-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
try buildmetrics for tracking builds #285
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
edulop91
approved these changes
Jun 12, 2019
Codecov Report
@@ Coverage Diff @@
## master #285 +/- ##
=======================================
Coverage 80.04% 80.04%
=======================================
Files 17 17
Lines 1408 1408
=======================================
Hits 1127 1127
Misses 160 160
Partials 121 121 Continue to review full report at Codecov.
|
palasha
pushed a commit
to palasha/fogg
that referenced
this pull request
Apr 7, 2020
try buildmetrics for tracking buildsI set out to try and find ways to instrument our builds and this is the best option I have found. This travis build will now use honeycomb's [buildmetrics](https://github.com/honeycombio/buildevents) to trace the build through its execution. We can then analyze the data and alert on any SLIs we care about. I looked at datadog integration, but their metrics don't include the branch name (because it is high cardinality), so you can't do things like "only alert on master branch failures". Honeycomb, with support for high-cardinality metrics should allow us to do this. ### Test Plan * travis build ### References * https://github.com/honeycombio/buildevents
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I set out to try and find ways to instrument our builds and this is the best option I have found.
This travis build will now use honeycomb's buildmetrics to trace the build through its execution. We can then analyze the data and alert on any SLIs we care about.
I looked at datadog integration, but their metrics don't include the branch name (because it is high cardinality), so you can't do things like "only alert on master branch failures". Honeycomb, with support for high-cardinality metrics should allow us to do this.
Test Plan
References