...
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
...
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
The On Kibana browser, Management → Index Pattersn → scripted fields, create the following two painless scripted fields need to be created 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.
...
- 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
