# Empty String on windows.service.start\_type field while using Metricbeat 7.8.0

**URL:** https://discuss.elastic.co/t/empty-string-on-windows-service-start-type-field-while-using-metricbeat-7-8-0/238056
**Category:** Beats
**Tags:** metricbeat
**Created:** [June 22, 2020, 9:42am UTC](https://discuss.elastic.co/t/empty-string-on-windows-service-start-type-field-while-using-metricbeat-7-8-0/238056 "2020-06-22T09:42:02Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![fadjar340](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fadjar340/32/43610_2.png) [@fadjar340](https://discuss.elastic.co/u/fadjar340)
#### Post date: [June 22, 2020, 9:53am UTC](https://discuss.elastic.co/t/empty-string-on-windows-service-start-type-field-while-using-metricbeat-7-8-0/238056/2 "2020-06-22T09:53:48Z")

</div>

Perhaps Beats team need to verify the module before released, as per my [posting](https://discuss.elastic.co/t/heartbeat-problem-in-7-7-x/237250/5) for heartbeat fields. Fortunately in the heartbeat fields, still have the data and just add processor copy\_fields, this metricbeat module break a lots of dashboard, I'm afraid.

I wish it will rectified in next minor release...

Regards,  
Fadjar Tandabawana

---

_[View the full topic](https://discuss.elastic.co/t/empty-string-on-windows-service-start-type-field-while-using-metricbeat-7-8-0/238056)._