kemko/nomad
1
0
Fork 0
mirror of https://github.com/kemko/nomad.git synced 2026-01-16 07:15:40 +03:00
Code Issues Packages Projects Releases Wiki Activity

docs: use of node_class when autoscaling (#14950)

Browse Source 
Document how the value of `node_class` is used during cluster scaling.

https://github.com/hashicorp/nomad-autoscaler/issues/255
This commit is contained in:
Luiz Aoqui
2022-10-21 10:35:45 -04:00
committed by GitHub
parent b52d40d46b
commit f2318ed2ec
1 changed files with 22 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
website/content/tools/autoscaling/plugins/apm/nomad.mdx
View File

@@ -59,8 +59,8 @@ check {
}
```
Querying Nomad task group metrics is be done using the `operation_metric` syntax,
where valid operations are:
Querying Nomad task group metrics is be done using the `<operation>_<metric>`
syntax, where valid operations are:
- `avg` - returns the average of the metric value across allocations in the task
group.
@@ -86,16 +86,30 @@ The metric value can be:
The Nomad APM allows querying Nomad to understand the current allocated resource
as a percentage of the total available.
~> **Note:** When using the Nomad APM plugin for cluster scaling, your policy `target` and
all Nomad clients intended to be targeted by the policy must have a
`node_class` defined. Nodes without `node_class` are evaluated using the
default class value `autoscaler-default-pool`.
```hcl
check {
source = "nomad-apm"
query = "percentage-allocated_cpu"
...
policy {
# ...
check {
source = "nomad-apm"
query = "percentage-allocated_cpu"
# ...
}
target "..." {
# ...
node_class = "autoscale"
# ..
}
}
```
Querying Nomad client node metrics is be done using the `operation_metric` syntax,
where valid operations are:
Querying Nomad client node metrics is be done using the `<operation>_<metric>`
syntax, where valid operations are:
- `percentage-allocated` - returns the allocated percentage of the desired
resource.