This repository was archived by the owner on Jan 22, 2026. It is now read-only.
Add grafana-annotation-resource - #20
Merged
Merged
Conversation
Signed-off-by: Toby Lorne <toby.lornewelch-richards@digital.cabinet-office.gov.uk>
YoussB
approved these changes
Jan 13, 2020
| @@ -0,0 +1,5 @@ | |||
| name: grafana-annotation-resource | |||
Contributor
There was a problem hiding this comment.
Hey @tlwr,
just a small change that I can do myself, we're intending to keep the name the same as you would use in a pipeline, so I will just remove the -resource from the name.
Let me know if this doesn't work for you and I will re-add it.
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Spiritual successor to concourse/resource-types-website#107 before repos were moved around.
What
Adds the grafana-annotation-resource built by @alphagov
Used for creating and updating Grafana annotations:

Image of a requests per second dashboard with Grafana annotations showing deployment phases
Why
We use Concourse for our many of our deployment pipelines, during which we run API and application availability tests.
It is useful to see the side-effects of these tests on our Grafana dashboards, e.g. elevated 5xx HTTP status codes. Given that Concourse is managing the pipeline, it makes sense to have a Concourse resource for creating/updating annotations.