From 71a1f59525ebdb06f6857a864162933988c0628d Mon Sep 17 00:00:00 2001 From: Adam Israel Date: Thu, 30 Mar 2017 20:48:13 -0400 Subject: [PATCH] Feature request: Metrics Collection Signed-off-by: Adam Israel --- Release3/vca-metrics-collection.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 Release3/vca-metrics-collection.md diff --git a/Release3/vca-metrics-collection.md b/Release3/vca-metrics-collection.md new file mode 100644 index 0000000..b3e12ea --- /dev/null +++ b/Release3/vca-metrics-collection.md @@ -0,0 +1,28 @@ +# Metrics Collection # + +## Proposer ## +- Adam Israel + +## Type ## +**Feature** + +## Target MDG/TF ## +VCA, DevOps, SO + +## Description ## +Operators prefer to make data-driven decisions. To aid this, I propose that we +begin collecting operational metrics from VNFs that make them available, via +push (collectd, statsd) or pull ([prometheus](https://prometheus.io/), etc). + +This metric data should be collected to a central data store. Once collected, +reports can be generated for the operator to view, and operational rules can be +defined with regard to notifications, auto-scaling and auto-healing. + + +## Demo or definition of done ## +- Selection of supported collection method(s) +- Creation of an OSM VNF METRICS charm layer to aid metrics collection +- The option to install metric collection during the installation process. +- Exposing a metrics dashboard (if supported by the supported collection + method(s), or the definition of of one or more reports to view relevant + metrics dtaa. -- 2.25.1