For the POI's layer of this pluggin, if you try to add fields to the tooltip, it works only in the cases that the field is at the 'root' level of the document, if not, it displays undefined. The reason is:
When you have field names like eventMessage.event.name, and you try to get the value of this field in the line 'dlContent += `
${field}
${hit._source[field]}
'
You get hit._source['eventMessage.event.name'], because kibana gives you that field name, and there is not key like that. Instead, the value must be gotten using the expression:
hit._source['eventMessage']['event']['name']
For this reason I added the function nestedField, that checks if the field has dots, and for each one, access to the property of the _source object one be one.
The image shows the result after apply the changes.
For the POI's layer of this pluggin, if you try to add fields to the tooltip, it works only in the cases that the field is at the 'root' level of the document, if not, it displays undefined. The reason is:
When you have field names like eventMessage.event.name, and you try to get the value of this field in the line 'dlContent += `
You get hit._source['eventMessage.event.name'], because kibana gives you that field name, and there is not key like that. Instead, the value must be gotten using the expression: hit._source['eventMessage']['event']['name'] For this reason I added the function nestedField, that checks if the field has dots, and for each one, access to the property of the _source object one be one.
The image shows the result after apply the changes.