Skip to content

Add metricsource commands and custom alert targets (metric alerts phase 2) - #67

Open
acoshift wants to merge 3 commits into
masterfrom
feat/custom-metrics
Open

Add metricsource commands and custom alert targets (metric alerts phase 2)#67
acoshift wants to merge 3 commits into
masterfrom
feat/custom-metrics

Conversation

@acoshift

@acoshift acoshift commented Sep 2, 2026

Copy link
Copy Markdown
Member

Summary

deploys metricsource set/get/list/delete/series/query for Prometheus scrape sources (SPEC-metric-alerts.md Phase 2; api pin 039b9e7c254328051faddb210ad58980b5ceb890).

  • set is a full upsert (-project -name -location -deployment -port -path default /metrics -disabled)
  • query takes repeatable -series and -timerange 1h|6h|12h|1d|7d|30d (default 1h)
  • alert create/update grow -kind deployment|custom, -source, -series; -metric also accepts value|rate
  • kind=custom leaves Location/Deployment empty (API requires them empty); update-merge seeds Kind/Source/Series from get
  • Help quotes '>=' / '<=' so shells do not treat them as redirections

Testing

No PR CI in this repo — verified locally: go test ./... && go vet ./... && go build green; deploys metricsource -h and deploys alert create -h mention kind/source.

deploys metricsource set/get/list/delete/series/query for Prometheus
scrape sources (SPEC-metric-alerts.md Phase 2). Set is a full upsert.

alert create/update grow -kind/-source/-series and accept value|rate
metrics for kind=custom. Update-merge seeds Kind/Source/Series from get.

Pin api to 039b9e7c254328051faddb210ad58980b5ceb890.
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.

1 participant