# ECS Quality Dashboard - ECS Coverage of LogSources

**URL:** <https://discuss.elastic.co/t/ecs-quality-dashboard-ecs-coverage-of-logsources/294806>\
**Category:** Kibana\
**Tags:** ecs-elastic-common-schema\
**Created:** [January 19, 2022, 11:53am UTC](https://discuss.elastic.co/t/ecs-quality-dashboard-ecs-coverage-of-logsources/294806 "2022-01-19T11:53:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![zangero98](https://avatars.discourse-cdn.com/v4/letter/z/a587f6/32.png) [@zangero98](https://discuss.elastic.co/u/zangero98)\
**Post date:** [January 19, 2022, 11:53am UTC](https://discuss.elastic.co/t/ecs-quality-dashboard-ecs-coverage-of-logsources/294806/1 "2022-01-19T11:53:50Z")

</div>

Hello 🙂

I'm searching for an ECS Dashboard Template to check if LogSources are sending the Logs right in view of ECS conditions (ECS coverage - [Elastic Security ECS field reference | Elastic Security Solution [7.16] | Elastic](https://www.elastic.co/guide/en/security/current/siem-field-reference.html))  
For example i would like to have a bar graph with all needed fields of the event taxonomy (category, type, outcome) in relation to all events. This should show whether the needed field are filled in (f.e. event.category:\*) and whether the allowed values are filled in. Host-, authentification- and and network fields would be important too.

Is there a template that matches something like that? 🙂  
The dashboard templates i found until now didn't realize this so i would be very thankful when someone would give me an advice.

---

<div class="post-metadata">

**Author:** ![ebeahan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebeahan/32/78989_2.png) [@ebeahan](https://discuss.elastic.co/u/ebeahan)\
**Post date:** [January 25, 2022, 10:39pm UTC](https://discuss.elastic.co/t/ecs-quality-dashboard-ecs-coverage-of-logsources/294806/2 "2022-01-25T22:39:56Z")

</div>

Hello, @zangero98!

I don't know of a dashboard template to show this type of ECS coverage. It is something the ECS team is still [tracking](https://github.com/elastic/ecs/issues/423). We're also always looking at better ways for users to validate their ingested data complies with ECS best practices.

Not a dashboard, but this [blog post](https://www.elastic.co/blog/validating-elastic-common-schema-fields-using-detection-rules) outlines an alternative solution using the security solution and detection rules. The examples from the piece are trying to solve the same problems you shared: missing fields or validating allowed values.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 22, 2022, 10:40pm UTC](https://discuss.elastic.co/t/ecs-quality-dashboard-ecs-coverage-of-logsources/294806/3 "2022-02-22T22:40:48Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.