I have checked the index template mapping and I do not have any mappings for this field.
I have met with this error a lot of times during the last few months.
I did not change the configuration regarding the index template, index pattern in beats .yml
I have not idea what I am doing wrong so my mapping set up from beasts have missing fields.
I have a similar issue with 7.7 filebeat cisco module, 7.8 metricbeat system module, as well as I, have with filebeat 7.9.2 netflow module
But the fields did not dynamically add. I just want to understand If the error in dashboards results from fields that are no longer used or it's something else?
Hi Adriann,
Did you refresh your Kibana index patterns?
I do not know the powershell dashboard but I do know the other one (User Management Events) because i was the one I did it.
Regarding to winlog.logon.id is a very useful field because it allows you to correlate different events performed by the same user, if it is not in the index pattern is dynamically generated (when you receive an event with that field) . From winlogbeat's Index Template:
In summary, if you have an index with winlog.logon.id field present and then you refresh your index pattern in kibana, the error in the user managment event dashboard should disappear
Thanks for your input.
I did refresh the indices and I saw some change in field numbers. But still, see the same error. Does this just must mean that kibana has never seen a document with that field?
Hi Adriann,
I did some extra test with a clean environment and here the explanation: when you first executewinlogbeat setup --index-management a winlogbeat index is created based on winlogbeat's index template. In that index pattern there is no definition for winlog.logon.id nor winlog.event_data.OldTargetUserName. That's why when you enter the first time to the dashboards the error appears.
Once you have real data containing values for winlog.logon.id and winlog.event_data.OldTargetUserName and you refresh the Kibana's index pattern the error will disappear.
Just to check, just rename a user in windows, so event 4781 is generated, refresh your index pattern and
I asked my friend to add a local user and change his name. The output shows some field but even after refreshing the index pattern this is the dashboard look.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.