Prometheus
PromQL queries for canary verification and deploy annotations.
At a glance
Section titled “At a glance”| Category | Observability |
| Authentication | None, bearer token or mTLS |
| Provider id | prometheus |
What it does
Section titled “What it does”- Canary verification queries
- Environment health signals
Set up
Section titled “Set up”- Create a read-only credential or enable workload identity for the metrics API.
- Add the integration in Slipway and run Test to execute a trivial query.
- Reference it from a canary
verificationblock byprovidername. - Dry-run the queries against a past deployment before relying on them.
Configuration
Section titled “Configuration”Illustrative configuration. Non-secret settings are stored as integration config; credentials are stored as encrypted Slipway secrets and referenced by name.
provider: prometheusconfig: url: https://prometheus.example.com bearer_token_secret: PROM_TOKENverification_query: | sum(rate(http_requests_total{service="api",status=~"5.."}[2m])) / sum(rate(http_requests_total{service="api"}[2m]))See Canary verification for how thresholds and intervals are evaluated.
Related
Section titled “Related”- Integrations overview
- Secrets for how credentials are stored and masked
- Webhooks and events for the events integrations subscribe to