# {"SystemTotalCpuProvider"} Failed instantiating PerformanceCounter

**URL:** <https://discuss.elastic.co/t/systemtotalcpuprovider-failed-instantiating-performancecounter/287298>\
**Category:** Beats\
**Created:** [October 21, 2021, 10:06am UTC](https://discuss.elastic.co/t/systemtotalcpuprovider-failed-instantiating-performancecounter/287298 "2021-10-21T10:06:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![joakim.aberg](https://avatars.discourse-cdn.com/v4/letter/j/ce7236/32.png) [@joakim.aberg](https://discuss.elastic.co/u/joakim.aberg)\
**Post date:** [October 21, 2021, 10:06am UTC](https://discuss.elastic.co/t/systemtotalcpuprovider-failed-instantiating-performancecounter/287298/1 "2021-10-21T10:06:11Z")

</div>

We get the following error on both our Staging and Production evironment. log.level:Error message:{"SystemTotalCpuProvider"} Failed instantiating PerformanceCounter - please make sure the current user has permissions to read performance counters. E.g. make sure the current user is member of the 'Performance Monitor Users' group.

We have added NT AUTHORITY\NETWORK SERVICE to 'Performance Monitor Users'-group and restarted servers. We have also tried recreating the performance counters with command "lodctr /r", but error still appears.

Any advice?

Using Elastic Cloud.

---

<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:** [November 18, 2021, 12:06pm UTC](https://discuss.elastic.co/t/systemtotalcpuprovider-failed-instantiating-performancecounter/287298/2 "2021-11-18T12:06:28Z")

</div>

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