Add Metrics to track Terraform state backend usage
Goal
Track number of Terraform state files we manage
Definition of done
- Add metric for total number of Terraform state files we manage
- Ensure events are reflected on a dashboard in Periscope
Notes
Pair with @nagyv-gitlab
Designs
- Show closed items
Is blocked by
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Nick Klick added to epic &2673
added to epic &2673
- Nick Klick mentioned in epic &2673
mentioned in epic &2673
- Nick Klick added workflowsolution validation + 1 deleted label
added workflowsolution validation + 1 deleted label
- Nick Klick changed the description
Compare with previous version changed the description
- Nick Klick added workflowblocked label and removed workflowsolution validation label
added workflowblocked label and removed workflowsolution validation label
- Nick Klick marked this issue as related to #207346 (closed)
marked this issue as related to #207346 (closed)
- Maintainer
Setting ~"devops::configure" based on ~"group::system".
- 🤖 GitLab Bot 🤖 added devopsconfigure [DEPRECATED] label
added devopsconfigure [DEPRECATED] label
- Viktor Nagy (GitLab) changed milestone to %12.10
changed milestone to %12.10
- Contributor
I see two options immediately:
- number of Terraform state files we manage
- number of times we write a state file (API requests)
I'd go for former: the number of Terraform state files we manage. This basically measures the number of Terraform projects built on our tooling.
What do you think?
- Viktor Nagy (GitLab) added workflowsolution validation label and removed workflowblocked label
added workflowsolution validation label and removed workflowblocked label
- Viktor Nagy (GitLab) assigned to @nagyv-gitlab and @nicholasklick
assigned to @nagyv-gitlab and @nicholasklick
- Viktor Nagy (GitLab) added workflowblocked label and removed workflowsolution validation label
added workflowblocked label and removed workflowsolution validation label
- Author Developer
@nagyv-gitlab Those seem like a good start.
Collapse replies - Contributor
@nicholasklick I'd choose just one metric, not 2. It should be an MVC after all.
- Nick Klick changed the description
Compare with previous version changed the description
- Nick Klick unassigned @nicholasklick
unassigned @nicholasklick
- Viktor Nagy (GitLab) changed the description
Compare with previous version changed the description
- Contributor
@nicholasklick Does it matter if we are on gitlab.com or on-prem? Can we use the same data collection mechanism (usage_ping)?
- Viktor Nagy (GitLab) unassigned @nagyv-gitlab
unassigned @nagyv-gitlab
- 🤖 GitLab Bot 🤖 added groupconfigure [DEPRECATED] label and removed 1 deleted label
added groupconfigure [DEPRECATED] label and removed 1 deleted label
- Viktor Nagy (GitLab) changed milestone to %13.0
changed milestone to %13.0
- Viktor Nagy (GitLab) added Deliverable label
added Deliverable label
- Nick Klick added workflowready for development label and removed workflowblocked label
added workflowready for development label and removed workflowblocked label
- 🤖 GitLab Bot 🤖 added [deprecated] Accepting merge requests label
added [deprecated] Accepting merge requests label
- Nick Klick assigned to @mattkasa
assigned to @mattkasa
- 🤖 GitLab Bot 🤖 removed [deprecated] Accepting merge requests label
removed [deprecated] Accepting merge requests label
- Matt Kasa mentioned in merge request !31280 (merged)
mentioned in merge request !31280 (merged)
- Dylan Griffith closed via merge request !31280 (merged)
closed via merge request !31280 (merged)
- Dylan Griffith mentioned in commit 24c9ac0e
mentioned in commit 24c9ac0e
- 🤖 GitLab Bot 🤖 changed the description
Compare with previous version changed the description
- 🤖 GitLab Bot 🤖 added groupenvironments label and removed groupconfigure [DEPRECATED] label
added groupenvironments label and removed groupconfigure [DEPRECATED] label