# SIEM - troubleshooting various error **URL:** \ **Category:** SIEM\ **Created:** [December 2, 2020, 1:05pm UTC](https://discuss.elastic.co/t/siem-troubleshooting-various-error/257358 "2020-12-02T13:05:54Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Frank\_Hassanabad](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frank_hassanabad/32/49255_2.png) [@Frank\_Hassanabad](https://discuss.elastic.co/u/Frank_Hassanabad)\ **Post date:** [December 3, 2020, 1:27am UTC](https://discuss.elastic.co/t/siem-troubleshooting-various-error/257358/2 "2020-12-03T01:27:25Z")
Your winlogbeat mappings aren't installed properly probably. See this thread for troubleshooting steps: > [@SIEM doesn't show any Winlogbeat events, despite ES receiving them](https://discuss.elastic.co/t/siem-doesnt-show-any-winlogbeat-events-despite-es-receiving-them/224008/9): > > Hi @aura, as you've discovered, it seems that some of your fields are not being mapped to the correct Elasticsearch [datatypes](https://www.elastic.co/guide/en/elasticsearch/reference/7.6/mapping-types.html). Elastic Common Schema (ECS) specifies that fields such as host.name must be of the [keyword](https://www.elastic.co/guide/en/elasticsearch/reference/7.6/keyword.html) datatype. Indeed, as you've also discovered, Elastic SIEM relies specifically on host.name to be present as a condition for populating many visualizations with host data. I'm not sure how familiar you are with Elasticsearch [mapping](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping.html) and [index templates](https://www.elastic.co/guide/en/elasticsearch/reference/7.6/indices-templates.html), as they can be challenging… --- _[View the full topic](https://discuss.elastic.co/t/siem-troubleshooting-various-error/257358)._