Skip to content
This repository has been archived by the owner on Sep 5, 2023. It is now read-only.

The user can declare how often a metric should be measured #5

Closed
mtneug opened this issue Nov 27, 2016 · 0 comments
Closed

The user can declare how often a metric should be measured #5

mtneug opened this issue Nov 27, 2016 · 0 comments

Comments

@mtneug
Copy link
Owner

mtneug commented Nov 27, 2016

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 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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant