-
Bug
-
Resolution: Done
-
Medium
-
Jakarta Release
Legacy VES Fault notofications (domain = fault, DMaap Topic = unauthenticated.SEC_FAULT_OUTPUT) are displayed in the Fault area of SDN-R, however Standards Defined Fault Notifications over VES ("domain": "stndDefined", "stndDefinedNamespace": "3GPP-FaultSupervision", topic = unauthenticated.SEC_3GPP_FAULTSUPERVISION_OUTPUT) - not displayed. At the same time, i see that this message successfuly forwarded to DMaap from VES collector - unauthenticated.SEC_3GPP_FAULTSUPERVISION_OUTPU.
Could you provide suggestion how to configure such solution.
See examples below:
Legacy VES Fault Notification:
{
"event": {
"commonEventHeader":
,
"faultFields": {
"faultFieldsVersion": "4.0",
"alarmCondition": "PilotNumberPoolExhaustion",
"eventSourceType": "other",
"specificProblem": "Calls cannot complete - pilot numbers are unavailable",
"eventSeverity": "CRITICAL",
"vfStatus": "Active",
"alarmAdditionalInformation":
}
}
}
Standards Defined VES Fault Notification:
{
"event": {
"commonEventHeader":
,
"stndDefinedFields": {
"schemaReference": "https://forge.3gpp.org/rep/sa5/MnS/blob/SA88-Rel16/OpenAPI/faultMnS.yaml#/components/schemas/NotifyNewAlarm",
"data":
,
"stndDefinedFieldsVersion": "1.0"
}
}
}
- relates to
-
DCAEGEN2-3272 More than 1 schema is valid. (code: 1023)
- Closed