You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 5, 2023. It is now read-only.
The pace of change is different for each metric. Also some services need to be autoscaled quicker than others (see #15). To accurately asses the current situation users must be able to specify how often spate should measure a specific metric. Users can set this rate on a per metric base. If no rate is set, the default one is used. The default can be set globally by an administrator.
Design
The measurement period is set per metric. spate looks for the label de.mtneug.spate.metrics.<key>.observer.period. The value has to be an time entry. The default period can be set via the CLI option --default-observer-period. If no is set 30s is used.
Example
# Setting the global default
$ spate --default-observer-period=10s
# Overwriting the default
$ docker service create \
--name service \
--label de.mtneug.spate.metrics.cpu.type=cpu \
--label de.mtneug.spate.metrics.cpu.observer.period=10s \
...
my/service
The text was updated successfully, but these errors were encountered:
Description
The pace of change is different for each metric. Also some services need to be autoscaled quicker than others (see #15). To accurately asses the current situation users must be able to specify how often spate should measure a specific metric. Users can set this rate on a per metric base. If no rate is set, the default one is used. The default can be set globally by an administrator.
Design
The measurement period is set per metric.
spate
looks for the labelde.mtneug.spate.metrics.<key>.observer.period
. The value has to be an time entry. The default period can be set via the CLI option--default-observer-period
. If no is set30s
is used.Example
The text was updated successfully, but these errors were encountered: