# Increasing VM monitoring time

**URL:** https://forum.opennebula.io/t/increasing-vm-monitoring-time/9771
**Category:** Operations
**Created:** [July 30, 2021, 10:00am UTC](https://forum.opennebula.io/t/increasing-vm-monitoring-time/9771 "2021-07-30T10:00:33Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Daniel\_Ruiz\_Molina](https://avatars.discourse-cdn.com/v4/letter/d/f08c70/32.png) [@Daniel\_Ruiz\_Molina](https://forum.opennebula.io/u/Daniel_Ruiz_Molina)
#### Post date: [July 30, 2021, 10:00am UTC](https://forum.opennebula.io/t/increasing-vm-monitoring-time/9771/1 "2021-07-30T10:00:33Z")

</div>

Hello,

I would like to increase VM monitoring time. By default, each 30 seconds OpenNebula runs a monitoring process for all VMs. In my scenario, sometimes server is running more than 450 VMs. I think that server could monitor in 300 seconds (5 minutes) interval. I have modified some parameters in /etc/one/monitord.conf:

```auto
#MANAGER_TIMER = 15
MANAGER_TIMER = 60
MONITORING_INTERVAL_HOST = 180
#HOST_MONITORING_EXPIRATION_TIME = 43200
HOST_MONITORING_EXPIRATION_TIME = 0
#VM_MONITORING_EXPIRATION_TIME = 43200
VM_MONITORING_EXPIRATION_TIME = 0

```

and other parameter in /etc/one/sched.conf

```auto
SCHED_INTERVAL = 30
MAX_VM = 50
###MAX_VM = 5000
MAX_DISPATCH = 30
MAX_HOST = 20

```

However, OpenNebula continues running a monitoring process each 30 seconds.

What have I done wrong?

Thanks.

---

<div class="post-metadata">

### Author: ![ruben](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/ruben/32/19_2.png) [@ruben](https://forum.opennebula.io/u/ruben)
#### Post date: [August 2, 2021, 12:01pm UTC](https://forum.opennebula.io/t/increasing-vm-monitoring-time/9771/2 "2021-08-02T12:01:00Z")

</div>

[https://docs.opennebula.io/6.0/installation\_and\_configuration/opennebula\_services/monitoring.html#adjust-monitoring-intervals](https://docs.opennebula.io/6.0/installation_and_configuration/opennebula_services/monitoring.html#adjust-monitoring-intervals)

I think you may be interested in the PROBES\_PERIOD attribute array. After changing it you need to restart the agents and opennebula.

---

<div class="post-metadata">

### Author: ![Daniel\_Ruiz\_Molina](https://avatars.discourse-cdn.com/v4/letter/d/f08c70/32.png) [@Daniel\_Ruiz\_Molina](https://forum.opennebula.io/u/Daniel_Ruiz_Molina)
#### Post date: [September 10, 2021, 8:44am UTC](https://forum.opennebula.io/t/increasing-vm-monitoring-time/9771/3 "2021-09-10T08:44:59Z")

</div>

Hi,

I have configured PROBES\_PERIOD array in this way:

> PROBES\_PERIOD = [  
> BEACON\_HOST = 120,  
> SYSTEM\_HOST = 600,  
> MONITOR\_HOST = 120,  
> STATE\_VM = 120,  
> MONITOR\_VM = 300,  
> SYNC\_STATE\_VM = 180  
> ]

but after restarting opennebula, opennebula-hem and opennebula-scheduler daemons, ONE is checking VM in a 30 seconds interval (old value), and not in 120 seconds interval (new value)…

---

<div class="post-metadata">

### Author: ![atodorov\_storpool](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/atodorov_storpool/32/5327_2.png) [@atodorov\_storpool](https://forum.opennebula.io/u/atodorov_storpool)
#### Post date: [September 15, 2021, 7:07am UTC](https://forum.opennebula.io/t/increasing-vm-monitoring-time/9771/4 "2021-09-15T07:07:26Z")

</div>

Hi,

The VM monitoring is done on the hosts so you should try restarting the monitoring daemon there too. Disable/enable the hosts and then an `onehost forceupdate` should restart the monitoring.

BR,  
Anton