...
- Timestamp (date formatted)
- RequestId (UUID)
- componentName (string)
- subComponent (string)
- loglevel (one of INFO, DEBUG, WARN, ERROR)
- vLogLevel (integer value assigned to each loglevel => INFO:1, DEBUG:23, WARN:35, ERROR:410)
- detailmessage (which is equivalent to the field message but aggregatable)
- source (log file path)
- Logger (logging object)
In case the fields for subComponent, vLogLevel, detailmessage do not appear, check and add the following part in the onap-pipeline.conf around the end of the filter. (Not necessary to restart logstash)
| Code Block |
|---|
ruby { code => " path = event.get('source').split('/') if path[5].include? 'log' event.set('subComponent', path[4]) else event.set('subComponent', path[5]) end event.set('component_subComponent', event.get('componentName') + '_' + event.get('subComponent')) case event.get('loglevel') when 'INFO' event.set('vLogLevel', 1) when 'DEBUG' event.set('vLogLevel', 3) when 'WARN' event.set('vLogLevel', 5) when 'ERROR' event.set('vLogLevel', 10) end " } mutate { add_field => { "detailmessage" => "%{message}" } } |
Create Kibana Scripted Fields
...