| Summary: | [RFE] Add finer grained monitoring thresholds for memory consumption on Hypervisors to RHV | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Ameya Charekar <achareka> |
| Component: | ovirt-engine | Assignee: | Ravi Nori <rnori> |
| Status: | CLOSED ERRATA | QA Contact: | Petr Matyáš <pmatyas> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.9 | CC: | apinnick, klaas, lsurette, lsvaty, mgoldboi, mperina, Rhev-m-bugs, rnori, srevivo |
| Target Milestone: | ovirt-4.3.0 | Keywords: | FutureFeature |
| Target Release: | 4.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-4.3.0_alpha | Doc Type: | Enhancement |
| Doc Text: |
In the Administration Portal, it is possible to set a threshold for cluster level monitoring as a percentage or an absolute value, for example, 95% or 2048 MB. When usage exceeds 95% or free memory falls below 2048 MB, a "high memory usage" or "low memory available" event is logged. This reduces log clutter for clusters with large (1.5 TB) amounts of memory.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-08 12:37:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1629592 | ||
| Bug Blocks: | |||
|
Description
Ameya Charekar
2018-03-24 00:39:43 UTC
The threshold can be changed using: engine-config -s LogMaxPhysicalMemoryUsedThresholdInPercentage=<VALUE> where <VALUE> is the percentage, when above message is logged. By default it's set to 95% (In reply to Martin Perina from comment #2) > The threshold can be changed using: > > engine-config -s LogMaxPhysicalMemoryUsedThresholdInPercentage=<VALUE> > > where <VALUE> is the percentage, when above message is logged. By default > it's set to 95% The request is: 1. Also in absolute numbers 2. Per cluster I think the 1st request is far more important than the first 2nd one. Ravi, shouldn't be those new LogMaxMemoryUsedThresholdType and LogMaxMemoryUsedThreshold be visible in engine-config? # engine-config -a | grep MemoryUsed LogMaxPhysicalMemoryUsedThresholdInPercentage: 95 version: general [root@10-37-140-204 ~]# yum list ovirt-engine Last metadata expiration check: 0:13:06 ago on Thu 20 Sep 2018 08:05:54 PM CEST. Installed Packages ovirt-engine.noarch 4.3.0-0.0.master.20180919131647.git219e0985a3b.fc28 @ovirt-master-snapshot (In reply to Pavol Brilla from comment #7) > Ravi, > > shouldn't be those new LogMaxMemoryUsedThresholdType and > LogMaxMemoryUsedThreshold be visible in engine-config? > > > # engine-config -a | grep MemoryUsed > LogMaxPhysicalMemoryUsedThresholdInPercentage: 95 version: general > [root@10-37-140-204 ~]# yum list ovirt-engine > Last metadata expiration check: 0:13:06 ago on Thu 20 Sep 2018 08:05:54 PM > CEST. > Installed Packages > ovirt-engine.noarch > 4.3.0-0.0.master.20180919131647.git219e0985a3b.fc28 > @ovirt-master-snapshot No, engine-config still contains the default in percentage with 95 as value. But users can change that value for each cluster when you create new or update existing cluster. UI elements found, will test further with host to check correct triggers Verified on ovirt-engine-4.3.0-0.8.rc2.el7.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:1085 |