Added an extra check to avoid NPE in OpenTraffic-Pipeline

Solves issue #101

Author: Chris Wiechmann

CHANGELOG.md

@@ -9,6 +9,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/).
 - TransactionData not shown, if TransactionElement legs are not in a row [#97](https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/issues/97)
 - Already existing ServiceName and Operation (Policy-Based) is removed during API-Lookup, when native API cannot be looked up [#98](https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/issues/98)
 - Data is deleted too early - Data is not visible anymore after ap. 7 days [#99](https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/issues/99)
+- Logstash Pipeline crashes with NullPointerException in some cases [#101](https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/issues/101)
 
 ### Added
 - Added a new parameter: `DISABLE_CUSTOM_PROPERTIES` to disable custom properties support [#95](https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/issues/95)

logstash/pipelines/OpenTrafficPipeline.conf

@@ -287,8 +287,9 @@ filter {
             remove_field => ["transactionElements"] 
           }
           # For some requests (OPTIONS, some native calls) the finalStatus is not set - Set it based on the http.status
+          # Extra check, if field [http][status] exists is a must (See https://github.com/elastic/logstash/issues/11917)
           if( ![finalStatus] ) {
-            if ([http][status] >= 200 and [http][status] <= 299 ) {
+            if ([http][status] and [http][status] >= 200 and [http][status] <= 299 ) {
               mutate { add_field => { "[finalStatus]" => "Pass" } }
             } else {
               mutate { add_field => { "[finalStatus]" => "Fail" } }