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

A replica metric can be the memory usage #18

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

A replica metric can be the memory usage #18

mtneug opened this issue Nov 27, 2016 · 0 comments

Comments

@mtneug
Copy link
Owner

mtneug commented Nov 27, 2016

Description

The memory usage is a general metric that is provided by Docker for each replica. It might not fully capture the state of a replica, but it can always be used even for applications that expose no other information. In spate the memory usage is a relative value between 0 and 1. It is also a metric type with a default value of 0.8. Users can only declare on memory usage metric per service.

Design

The replica metric memory usage is also its own metric type called memory. Using it only requires that the label de.mtneug.spate.metrics.<key>.type=memory is present. This metric type can only be used once. Using it multiple times results in a deactivation of autoscaling and an error logs message. The default target value of 0.8 can be overwritten.

Example

$ docker service create \
   --name service \
   --label de.mtneug.spate.metrics.memory.type=memory \
   --label de.mtneug.spate.metrics.memory.target=0.7 \
   ...
   my/service
@mtneug mtneug modified the milestone: 0.1.0 Nov 27, 2016
@mtneug mtneug self-assigned this Nov 27, 2016
@mtneug mtneug changed the title An instance metric can be the memory usage A replica metric can be the memory usage Nov 30, 2016
@mtneug mtneug modified the milestones: 0.2.0, 0.1.0 Dec 1, 2016
@mtneug mtneug closed this as completed Oct 20, 2019
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