summaryrefslogtreecommitdiffstats
path: root/docs/files/VESEventListener.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/files/VESEventListener.rst')
-rw-r--r--docs/files/VESEventListener.rst12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/files/VESEventListener.rst b/docs/files/VESEventListener.rst
index 1157f24..a396e5c 100644
--- a/docs/files/VESEventListener.rst
+++ b/docs/files/VESEventListener.rst
@@ -1,7 +1,7 @@
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. Copyright 2017 AT&T Intellectual Property, All rights reserved
-.. Copyright 2017 Huawei Technologies Co., Ltd.
+.. Copyright 2017-2018 Huawei Technologies Co., Ltd.
=============================
Service: *VES Event Listener*
@@ -47,7 +47,7 @@ commonEventHeader, as specified below:
- 'Tca'for the thresholdCrossingAlert domain
- 'voiceQuality'for the voiceQuality domain
-Sdc (the ONAP Service Design and Creation environment) defines and catalogs specific services, VNFs, VF modules and other entities, which are generically referred to as 'Sdc models'. The Sdc model that an event is associated with should be indicated in the second subfield within the eventName. If the event is not associated with an Sdc model but is instead being generated by an application platform like SO, then a string identifying the Application Platform may be used instead. In either case, all subfield names should be converted to camel case format (with no spaces, hyphens or underscores).
+SDC (the ONAP Service Design and Creation environment) defines and catalogs specific services, VNFs, VF modules and other entities, which are generically referred to as 'SDC models'. The SDC model that an event is associated with should be indicated in the second subfield within the eventName. If the event is not associated with an Sdc model but is instead being generated by an application platform like SO, then a string identifying the Application Platform may be used instead. In either case, all subfield names should be converted to camel case format (with no spaces, hyphens or underscores).
The final subfield of the eventName name should describe, in a compact camel case format (with no spaces, hyphens or underscores), the specific information being conveyed by the event. In some cases, this final subfield will not be required (e.g., in the case of Heartbeats or in the case of an event source which, for a domain like syslog, defines only one eventName to support it):
@@ -60,7 +60,7 @@ Examples of eventNames following the naming standards are provided below:
- Tca\_vDbe\_CpuThresholdExceeded
- Other\_SO\_InstantiationPhase1Complete
-Any questions about the naming of eventNames should be resolved as part of service and resource onboarding to the ONAP Service Design and Creation environment (i.e., Sdc).
+Any questions about the naming of eventNames should be resolved as part of service and resource onboarding to the ONAP Service Design and Creation environment (i.e., SDC).
Support for Protocols Other Than HTTPS
--------------------------------------
@@ -1170,7 +1170,7 @@ The gtpPerFlowMetrics datatype consists of the following fields:
+------------------------------------+---------------------+-------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| numPacketsTransmittedInclRetrans | number | Yes | number of packets transmitted, including retransmissions |
+------------------------------------+---------------------+-------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| numRetries | number | Yes | number of packet retrie |
+| numRetries | number | Yes | number of packet retries |
+------------------------------------+---------------------+-------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| numTimeouts | number | Yes | number of packet timeouts |
+------------------------------------+---------------------+-------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
@@ -1281,7 +1281,7 @@ following fields:
+-----------------------------+-----------------------+-------------+---------------------------------------------------------------+
| correlator | string | Yes | Constant across all events on this call |
+-----------------------------+-----------------------+-------------+---------------------------------------------------------------+
-| localIpAddress | string | Yes | Ip address on VNF |
+| localIpAddress | string | Yes | IP address on VNF |
+-----------------------------+-----------------------+-------------+---------------------------------------------------------------+
| localPort | string | Yes | Port on VNF |
+-----------------------------+-----------------------+-------------+---------------------------------------------------------------+
@@ -1496,7 +1496,7 @@ REST Operation Summary
Table - REST Operation Summary
-Api Version
+API Version
~~~~~~~~~~~
apiVersion is used to describe the major version number of the event