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

Add Prometheus provider for external metrics check during autoscaling #104

Merged
merged 4 commits into from
Nov 13, 2019

Conversation

jrasell
Copy link
Owner

@jrasell jrasell commented Nov 11, 2019

A scaling policy can now contain external checks which pull a metric value from an external provider and evaluate this agains the threshold configured. If the threshold is broken, the configured action will be requested.

The change also makes the Nomad resource calculation checks optional when running the autoscaler, allowing user to only use external checks if they wish or a combination. The autoscaler does a number of decision steps, in order to make sure both Nomad and external check evaluations are taken into account before requesting action.

closes #102

A scaling policy can now include a list of external checks which
are evaluated during the autoscaling run. Initially Prometheus
can be used, but additional providers can be added providing the
policy is updated and the metrics interface is statisfied.
@jrasell jrasell added kind/enhancement Issues relating to enhancements area/policy-engine Issues related to the policy engine area/autoscaling Issues related to internal autoscaling labels Nov 11, 2019
@jrasell jrasell self-assigned this Nov 11, 2019
@jrasell jrasell merged commit 114932f into master Nov 13, 2019
@jrasell jrasell deleted the gh-102 branch November 13, 2019 08:10
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/autoscaling Issues related to internal autoscaling area/policy-engine Issues related to the policy engine kind/enhancement Issues relating to enhancements
Projects
None yet
Development

Successfully merging this pull request may close these issues.

autoscaler: allow use of custom metric sources in autoscaler evaluation
1 participant