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

feat: Introduce activationTargetValue for MS SQL Scaler #822

Merged
merged 1 commit into from
Jul 19, 2022
Merged

feat: Introduce activationTargetValue for MS SQL Scaler #822

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
2 changes: 2 additions & 0 deletions content/docs/2.8/scalers/mssql.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ triggers:
connectionStringFromEnv: MSSQL_CONNECTION_STRING
query: "SELECT COUNT(*) FROM backlog WHERE state='running' OR state='queued'"
targetValue: "5.5"
activationTargetValue: '5'
metricName: backlog_process_count # optional - the generated value would be `mssql-{sha256hash}`
```

Expand All @@ -43,6 +44,7 @@ The `mssql` trigger always requires the following information:

- `query` - A [T-SQL](https://docs.microsoft.com/sql/t-sql/language-reference) query that returns a single numeric value. This can be a regular query or the name of a stored procedure.
- `targetValue` - A threshold that is used as `targetValue` or `targetAverageValue` (depending on the trigger metric type) in the Horizontal Pod Autoscaler (HPA). (This value can be a float)
- `activationTargetValue` - Target value for activating the scaler. Learn more about activation [here](./../concepts/scaling-deployments.md#activating-and-scaling-thresholds).(Default: `0`, Optional, This value can be a float)

To connect to the MSSQL instance, you can provide either:

Expand Down