# Running Metricbeat for a long time everyday at the same time

**URL:** <https://discuss.elastic.co/t/running-metricbeat-for-a-long-time-everyday-at-the-same-time/184800>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [June 7, 2019, 6:09pm UTC](https://discuss.elastic.co/t/running-metricbeat-for-a-long-time-everyday-at-the-same-time/184800 "2019-06-07T18:09:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![EZprogramming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ezprogramming/32/57291_2.png) [@EZprogramming](https://discuss.elastic.co/u/EZprogramming)\
**Post date:** [June 7, 2019, 6:09pm UTC](https://discuss.elastic.co/t/running-metricbeat-for-a-long-time-everyday-at-the-same-time/184800/1 "2019-06-07T18:09:17Z")

</div>

Hi everyone,

**Brief background about my problem:**

I need to run Metricbeat on my machine that is located in a different region (I don't live there), and that region does not have a reliable wifi connection. I need to receive performance metrics about the system module and visually view it through Kibana.

**Questions:**

1. Is there any way to run Metricbeat for a long time everyday at a specific time such as 8am - 6pm? You can provide all your suggestions and I can explore them. The one I know is running it in a docker on EC2 instance, but that needs reliable wifi connection.

2. What happens if Metricbeat fails, can it reset on its own? As you know I don't have access to the machine, so I need it to do this automatically.

3. Is there a way to show Metricbeat performance data such as CPU and Memory usage directly in Kibana APM or Kibana dashboards wihtout dealing with Elasticsearch metrics documentations?

I appreciate any feedback/suggestions, we can all learn together. 😀

---

<div class="post-metadata">

**Author:** ![exekias](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/exekias/32/28718_2.png) [@exekias](https://discuss.elastic.co/u/exekias)\
**Post date:** [June 14, 2019, 8:41am UTC](https://discuss.elastic.co/t/running-metricbeat-for-a-long-time-everyday-at-the-same-time/184800/2 "2019-06-14T08:41:50Z")

</div>

Hi @EZprogramming,

Metricbeat doesn't implement mechanisms for scheduling or restarting itself, as this is normally handled by the operative system.

Have you considered configuring a cron job to launch metricbeat when you need it? you can probably script something to stop it after a while, for instance, by sending a TERM signal to the metricbeat process.

If you setup Metricbeat dashboards you should be able to see system info (including CPU/mem) in the system dashboard.

---

<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:** [July 12, 2019, 8:41am UTC](https://discuss.elastic.co/t/running-metricbeat-for-a-long-time-everyday-at-the-same-time/184800/3 "2019-07-12T08:41:54Z")

</div>

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