-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
Jakarta Release
-
None
Step to reproduce:-
SDNR Faults not storing the complete details of the faults generated by device.
Following data is missing
- fault-id
- fault-source
- affected-objects
- fault-severity – showing incorrect value than what
From SMO UI Fault-id and name are missing in Faults page. Need to add these fields to the Faults page.
Findings:-
Some notification fields already available in the Elasticsearch DB with different names and the remaining one we are planning to add so that it will be available on the REST API and UI enhancements can be done later.
Following is the mapping between fields stored in DB table vs API response
fault-source: Mapped to object-id in the response.
fault-severity: Mapped to severity. If is-cleared=true,then its value is Non-Alarmed.
fault-text: Mapped to problem
fault-id and affected-objects are not returned by API. We need to add these two fields to the DB.
fault-id: This is being stored by the name of the field is id and in the final ES response this is being replaced with ED id. We are planning to introduce another field fault-id in ES table.
affected-objects: This is not being stored now and we will store it in ES. This is list contain list of source names. Currently couldn’t find a way to store the list hence planning to store it as String in DB wtih comma(,) seperated values.
Solution:-
After adding fault id and affected-objects-str new response is
{
"data-provider:output": {
"data": [
,
],
"pagination":
}
}
and from UI fault-id and affected-objects are added