Skip to content
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.

Sign up for GitHub

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

Jump to bottom

update Prometheus docs #528

Merged
merged 1 commit into from
Sep 20, 2021
Merged

update Prometheus docs #528

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions content/docs/2.5/scalers/prometheus.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,17 +15,17 @@ This specification describes the `prometheus` trigger that scales based on a Pro
triggers:
- type: prometheus
metadata:
# Required
# Required fields:
serverAddress: http://<prometheus-host>:9090
metricName: http_requests_total
metricName: http_requests_total # Note: name to identify the metric, generated value would be `prometheus-http_requests_total`
query: sum(rate(http_requests_total{deployment="my-deployment"}[2m])) # Note: query must return a vector/scalar single element response
threshold: '100'
```

**Parameter list:**

- `serverAddress` - Address of Prometheus
- `metricName` - Metric name to use
- `serverAddress` - Address of Prometheus server
- `metricName` - Name to identify the Metric in the external.metrics.k8s.io API. If using more than one trigger it is required that all `metricName`(s) be unique.
- `query` - Query to run
- `threshold` - Value to start scaling for

Expand Down