Two dashboards are provided for the monitoring of failure and success flows specifically during the process of SDC service onboarding. The flow is based on the values coming from the field "ACTION" and the failure or success is determined by the field "STATUS".
If we give an idea about the values of the two fields, our test lab shows the following variation for the fields ACTION and STATUS respectively.
Data Requirements
The dashboards provided here uses the following data fields. Note: DESC and MODIFIER are not mandatory.
- Timestamp
- ACTION
- STATUS
- DESC
- MODIFIER
This monitoring tool is based on Beijing version but subject to data availability from the system. If the required data fields are not available, the user would try to make those fields available by modifying onap-pipelie.conf or logback.xml files, which is out of scope of this document.
Create Scripted Fields
On Kibana browser, Management → Index Pattersn → scripted fields, create the following two painless scripted fields against the index pattern "logstash-*".
| Field Name | Type | Script code | Description |
|---|---|---|---|
| flowStatus | string | if (doc.containsKey('STATUS.keyword') && !doc['STATUS.keyword'].empty) { if (doc.containsKey('ACTION.keyword')) { if (doc['STATUS.keyword'].value =~ /NOTIFIED/) return null; if (doc['STATUS.keyword'].value =~ /(20?)|(DEPLOYED)|(_OK)/) return "Flow_Success"; else if (doc['STATUS.keyword'].value =~ /(40?)|(50?)|(ERROR)|(NOT_)/) return "Flow_Failure"; } } return null; | Determines the flow status to be either Flow_Success or Flow_Failure based on STATUS info |
| RequestId_UUID | string | if (doc.containsKey('RequestId.keyword')) return doc['RequestId.keyword'].value; else if (doc.containsKey('UUID.keyword')) return doc['UUID.keyword'].value; | In the absence of RequestId, reports the UUID if available |
For the sake of performanceof Kibana queries, the user could include these fields into the onap-pipeline.conf.
Import Kibana Object
On Kibana browser, import this Kibana object file (json) on Management → Saved Objects → Import.
Dashbaord 1: SDC Flow Failure Monitoring
- The user can set the time picker for the interested interval
- Dashboard shows the count of failed flows in terms of count of unique Timestamp
- The over-time display highlights when the failures happened for which flows
- The table on bottom lists those failure cases with detail information
- If available, the user could take the associated RequestId to the Culprit Locator for further investigation of the issue.
Dashboard 2: SDC Flow Success & Failure Statistics
- This dashboard reports the total success and failure counts for the specified time period
- Highlights which flows tend to fail more frequently than the others
