-
Story
-
Resolution: Done
-
Medium
-
None
-
None
Goal:
2nd stage of validation in VES Collector is dedicated to check the validity of events transferred as payload of VES stndDefined messages. It is expected to improve the troubleshooting of network functions, which bring standards-defined notifications to ONAP.
- VES Collector is enhanced with the 2nd stage of JSON documents validation
- In case a configurable parameter (controlling 2nd stage of validation) is enabled
- VES collector executes the 2nd stage of validation:
- If the parameter mentioned before allows for that validation action
- If the stndDefinedFields.schemaReference parameter is present
- If the stndDefinedFields.schemaReference points to a valid schema stored in associated repository
- Following are characteristics of 2nd stage of validation
- 2nd stage validation - covers contents of stndDefinedFields.data property
- 2nd stage validation - is executed with cached schemas, to reduce impact on validation performance
- Error cases are covered (at least those):
- stndDefinedFields.data empty
- schema reffered by stndDefinedFields.schemaReference doesn`t exist of is inaccessbile
- Absence of stndDefinedFields.schemaReference is a normal case (parameter is optional).
- relates to
-
OOM-2589 Add externalSchemaRepo generation script to OOM/contrib
- Closed
-
DCAEGEN2-1769 Add stndDefined domain to VES Collector
- Closed