Klibs: add DigitalOcean metrics agent #2007
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This new klib implements an agent which, similarly to the DigitalOcean agent at https://github.com/digitalocean/do-agent, collects memory usage metrics (consisting of values for total, free, cached and available memory) and sends them to the DigitalOcean monitoring server.
This klib is configured via a "digitalocean" tuple in the manifest options: sending of memory metrics is enabled when this tuple contains a "metrics" tuple. The default interval between two successive metrics data points is 120 seconds; the "metrics" configuration tuple may contain an "interval" option to specify an arbitrary interval value, expressed in seconds.
Example snippet of Ops configuration:
Note: when the DigitalOcean klib is configured to send memory metrics, CPU and disk I/O metrics are not displayed in the graphs of the DigitalOcean droplet control panel.