2 .. Copyright (c) 2019 AT&T Intellectual Property.
4 .. Copyright (c) 2019 Nokia.
7 .. Licensed under the Creative Commons Attribution 4.0 International
9 .. Public License (the "License"); you may not use this file except
11 .. in compliance with the License. You may obtain a copy of the License at
14 .. https://creativecommons.org/licenses/by/4.0/
17 .. Unless required by applicable law or agreed to in writing, documentation
19 .. distributed under the License is distributed on an "AS IS" BASIS,
21 .. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
23 .. See the License for the specific language governing permissions and
25 .. limitations under the License.
29 VESPA Manager Overview
30 ======================
32 The VESPA Manager uses the VES Agent (https://github.com/nokia/ONAP-VESPA) to adapt near-RT RIC internal statistics' collection using Prometheus to scrape metrics from platform and xApp microservices and forward to ONAP or VES Collector via VES interface (VNF event streaming).
34 The VESPA Manager deployment runs two processes: the VESPA manager and the VES Agent (i.s. VESPA). The VESPA manager starts and configures the VES Agent.
35 The VES Agent is a service acting as a bridge between Prometheus and ONAP / VES Collector.
37 Application Metrics Definition
38 ==============================
40 The application metrics are defined in the application descriptor. For each counter, the following fields are required in the "metrics" section of the descriptor:
42 * name - Prometheus name of the counter
43 * objectName - object name in VES
44 * objectInstance - object instance in VE
46 The VESPA manager receives the application metrics configuration from the application manager. It subscribes the app notification messages from the application manager, and after having received one, requests the latest application configuration, creates the VES Agent configuration based on it,
47 and restarts the VES Agent.
49 The VES Agent does not report any other metrics to VES.
51 Prometheus Configuration
52 ========================
54 The VES Agent reads the ricComponentName from Prometheus label
57 VES Collector Event Format
58 ==========================
60 The VES Agent transmits events to the VES Collector in the VES Common Event Format v5.4.1. The Common Event Format is expressed in JSON schema v28.4.1.
62 VES Event Listener 5.4.1:
63 earlier under h t t p s://docs.onap.org/en/casablanca/submodules/vnfsdk/model.git/docs/files/VESEventListener.html
66 <https://github.com/nokia/ONAP-VESPA/blob/8e9d9e93bb00bed0f5402c9de9502385d5e80acc/doc/CommonEventFormat_28.4.1.json>
71 The VESPA manager container requires the following environment variables:
73 * VESMGR_VNFNAME - VNF name as a string. Default: Vespa.
74 * VESMGR_NFNAMINGCODE - NF naming code as a string. Default: ricp.
75 * VESMGR_HB_INTERVAL - VES heartbeat interval as a string. For example: 30s.
76 * VESMGR_MEAS_INTERVAL - Measurement interval as a string. For example: 60s.
77 * VESMGR_PROMETHEUS_ADDR - Prometheus address. For example: h t t p://127.0.0.1:123
78 * VESMGR_ALERTMANAGER_BIND_ADDR - Bind address to receive alerts from Prometheus AlertManager
80 * VESMGR_PRICOLLECTOR_ADDR - Primary collector FQDN as a string. For example: ricaux-entry.
81 * VESMGR_PRICOLLECTOR_PORT - Primary collector port id as an integer. Default: 8443.
82 * VESMGR_PRICOLLECTOR_SERVERROOT - Path before the /eventListener part of the POST URL as a string.
83 * VESMGR_PRICOLLECTOR_TOPIC - Primary collector topic as a string.
84 * VESMGR_PRICOLLECTOR_SECURE - Use HTTPS for VES collector. Possible string values: true or false.
85 * VESMGR_PRICOLLECTOR_USER - User name as a string.
86 * VESMGR_PRICOLLECTOR_PASSWORD - Password as a string.
87 * VESMGR_PRICOLLECTOR_PASSPHASE - Passphrase as a string.
89 * VESMGR_APPMGRDOMAIN - Application manager domain. This is for testing purposes, only. Default: service-ricplt-appmgr-http.ricplt.svc.cluster.local.
94 The VESPA manager replies to liveness HTTP GET at path /supervision.
99 The VESPA manager exits in the following error cases:
101 * The VES Agent exits
102 * An unrecoverable system error during the initialization, for example
103 * Creation of the VES Agent configuration file fails
104 * Creation of a HTTP request message fails
109 In order to run the VESPA manager unit tests, give the following command: