Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

F #1324: Option to not store monitoring data to the DB #656

Merged
merged 4 commits into from
Jun 14, 2019
Merged

F #1324: Option to not store monitoring data to the DB #656

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
bababa3
F #1324: Add MONITORING_INTERVAL_DB_UPDATE field to oned.conf
Jun 13, 2019
550399b
F #1324: Update resolver issues
Jun 13, 2019
b1f6804
Update resolved_issues_583.rst
Jun 14, 2019
4a69953
Merge branch 'one-5.8-maintenance' into feature-1324
Jun 14, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 15 additions & 13 deletions source/deployment/open_cloud_host_setup/monitoring.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,19 +93,21 @@ Monitoring Configuration Parameters

OpenNebula allows to customize the general behavior of the whole monitoring subsystem:

+-------------------------------+--------------------------------------------------------------------------------------------------------------+
| Parameter | Description |
+===============================+==============================================================================================================+
| MONITORING_INTERVAL_HOST | Time in seconds between host monitorization. It must have a value greater than the manager timer |
+-------------------------------+--------------------------------------------------------------------------------------------------------------+
| MONITORING_INTERVAL_VM | Time in seconds between VM monitorization. It must have a value greater than the manager timer |
+-------------------------------+--------------------------------------------------------------------------------------------------------------+
| MONITORING_INTERVAL_DATASTORE | Time in seconds between Datastore monitorization. It must have a value greater than the manager timer |
+------------------------+---------------------------------------------------------------------------------------------------------------------+
| MONITORING_INTERVAL_MARKET | Time in seconds between marketplace monitorization. It must have a value greater than the manager timer |
+-------------------------------+--------------------------------------------------------------------------------------------------------------+
| HOST_PER_INTERVAL | Number of hosts monitored in each interval. |
+-------------------------------+--------------------------------------------------------------------------------------------------------------+
+-------------------------------+-------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description |
+===============================+=========================================================================================================================+
| MONITORING_INTERVAL_HOST | Time in seconds between host monitorization. It must have a value greater than the manager timer |
+-------------------------------+-------------------------------------------------------------------------------------------------------------------------+
| MONITORING_INTERVAL_DB_UPDATE | Time in seconds between DB writes of VM monitoring information. -1 to disable DB updating and 0 to write every update |
+-------------------------------+-------------------------------------------------------------------------------------------------------------------------+
| MONITORING_INTERVAL_VM | Time in seconds between VM monitorization. It must have a value greater than the manager timer |
+-------------------------------+-------------------------------------------------------------------------------------------------------------------------+
| MONITORING_INTERVAL_DATASTORE | Time in seconds between Datastore monitorization. It must have a value greater than the manager timer |
+-------------------------------+-------------------------------------------------------------------------------------------------------------------------+
| MONITORING_INTERVAL_MARKET | Time in seconds between marketplace monitorization. It must have a value greater than the manager timer |
+-------------------------------+-------------------------------------------------------------------------------------------------------------------------+
| HOST_PER_INTERVAL | Number of hosts monitored in each interval. |
+-------------------------------+-------------------------------------------------------------------------------------------------------------------------+

.. _monitoring_troubleshooting:

Expand Down
3 changes: 2 additions & 1 deletion source/intro_release_notes/release_notes_hotfix/resolved_issues_583.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ The following new features has been backported to 5.8.3:
- `Allow FILES in vCenter context <https://github.com/OpenNebula/one/issues/964>`__.
- `Allow alternative search base for ldap groups <https://github.com/OpenNebula/one/issues/3366>`__.
- `Show the federation index in onezone list command <https://github.com/OpenNebula/one/issues/3378>`__. If you want to enable this column, please update your `/etc/one/cli/onezone.yaml <https://github.com/OpenNebula/one/blob/master/src/cli/etc/onezone.yaml>`__ file.
- `Add an option to configure write frecuency of monitoring VM data to the DB <https://github.com/OpenNebula/one/issues/1324>`__.

The following issues has been solved in 5.8.3:

Expand All @@ -28,6 +29,6 @@ The following issues has been solved in 5.8.3:
- `Fix error in onegate when trying to make an operation in an specific VM <https://github.com/OpenNebula/one/issues/2047>`__.
- `Fix an error that propagates local quota information to other zones <https://github.com/OpenNebula/one/issues/3409>`__.
- `Fix LXD not handling disk mapping exceptions properly <https://github.com/OpenNebula/one/issues/3406>`__.
- `Reduce the ammount of database disk space generated by VM search indexes <https://github.com/OpenNebula/one/issues/3393>`__.
- `Reduce the amount of database disk space generated by VM search indexes <https://github.com/OpenNebula/one/issues/3393>`__.
- `Fix VM can't boot due to invalid cdrom config <https://github.com/OpenNebula/one/issues/3225>`__.
- `Fix wrong monitor of VMs without default VM_PREFIX in name <https://github.com/OpenNebula/one/issues/3430>`__.