# \[Ubuntu\] Metricbeat Service Privilege Levels

**URL:** <https://discuss.elastic.co/t/ubuntu-metricbeat-service-privilege-levels/158668>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [November 29, 2018, 12:55am UTC](https://discuss.elastic.co/t/ubuntu-metricbeat-service-privilege-levels/158668 "2018-11-29T00:55:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mhasanbulli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mhasanbulli/32/20653_2.png) [@mhasanbulli](https://discuss.elastic.co/u/mhasanbulli)\
**Post date:** [November 29, 2018, 12:55am UTC](https://discuss.elastic.co/t/ubuntu-metricbeat-service-privilege-levels/158668/1 "2018-11-29T00:55:31Z")

</div>

Hello,

As part of our internal standards for Linux (Ubuntu) VMs, when it is necessary to install a service, we create a user account, assign that user account to security groups and run that new service using that particular user account. This makes things like "who ran what" easier to track.

We have some development boxes that we would like to monitor using Metricbeat. The things we monitor are default system.yml and mysql.yml content.

For this type monitoring, what is the minimum privilege level we need to provide to Metricbeat? Does Metricbeat require sudo privileges all the time? Or, can we get away with less privileged accounts?

---

<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:** [December 27, 2018, 12:55am UTC](https://discuss.elastic.co/t/ubuntu-metricbeat-service-privilege-levels/158668/2 "2018-12-27T00:55:34Z")

</div>

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