summaryrefslogtreecommitdiffstats
path: root/docs/sections/services/ves-hv/design.rst
diff options
context:
space:
mode:
authorFilip Krzywka <filip.krzywka@nokia.com>2019-03-19 15:53:15 +0100
committerFilip Krzywka <filip.krzywka@nokia.com>2019-04-11 11:33:05 +0200
commit12acf3e8deaf15c6e5263b2b402c966f495057f1 (patch)
tree4afa68c835536413d4d8290856659cebeb0dc1c7 /docs/sections/services/ves-hv/design.rst
parent580eae246a3ac7bf9533df96d20c0fc9b5425d3c (diff)
Update HV-VES documentation
- include changes to collector configuration, especially moving from command line parameters to configuration file - include changes to run-time configuration i.e. moving from direct Consul requests to CBS usage - changes in design.rst cover extraction of protofiles from hv-ves repository to sdk - also swapped rstTable to rstCSVTable in deployment.rst as they are easier to maintain Change-Id: I5cdee7170d03edaf31615e40f6cb6ad14a6a2331 Issue-ID: DCAEGEN2-1352 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
Diffstat (limited to 'docs/sections/services/ves-hv/design.rst')
-rw-r--r--docs/sections/services/ves-hv/design.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/sections/services/ves-hv/design.rst b/docs/sections/services/ves-hv/design.rst
index a6c2b864..fb4fa2c7 100644
--- a/docs/sections/services/ves-hv/design.rst
+++ b/docs/sections/services/ves-hv/design.rst
@@ -33,13 +33,13 @@ The proto file (with the VES CommonHeader) comes with a binary-type **Payload**
Domain-specific data are encoded as well with GPB. A domain-specific proto file is required to decode the data.
This domain-specific proto has to be shared with analytics applications - HV-VES does not analyze domain-specific data.
-In order to support the RT-PM use-case, HV-VES includes a **perf3gpp** domain proto file. Within this domain, high volume data are expected to be reported to HV-VES collector.
+In order to support the RT-PM use-case, HV-VES uses a **perf3gpp** domain proto file. Within this domain, high volume data are expected to be reported to HV-VES collector.
Additional domains can be defined based on existing VES domains (like Fault, Heartbeat) or completely new domains. New domains can be added when needed.
GPB proto files are backwards compatible, and a new domain can be added without affecting existing systems.
Analytics applications have to be equipped with the new domain-specific proto file as well.
-Currently, these additional, domain specific proto files can be added to respective repos of HV-VES collector.
+Currently, these additional, domain specific proto files can be added to hv-ves-client protobuf library repository (artifactId: hvvesclient-protobuf).
Implementation details
----------------------