Thursday, 2020-03-12

*** openstackstatus has joined #openstack-telemetry00:44
*** ChanServ sets mode: +v openstackstatus00:44
*** psachin has joined #openstack-telemetry03:37
*** tesseract has joined #openstack-telemetry08:08
*** bengates has joined #openstack-telemetry08:09
*** witek_ has joined #openstack-telemetry09:13
*** saska has joined #openstack-telemetry09:14
saskaHi, does anybody know whether is it possible for Monasca to collect metrics mentioned in the following link? https://opendev.org/openstack/watcher/src/branch/master/watcher/decision_engine/datasources/monasca.py#L31 If it is not possible, what is missing in Monasca's code (or architecture) which would make it possible?09:20
witek_saska: some of these metrics are available via native Monasca checks09:25
witek_https://github.com/openstack/monasca-agent/blob/master/docs/Plugins.md#agent-plugin-detail09:26
witek_https://github.com/openstack/monasca-agent/blob/master/docs/Libvirt.md#per-instance-metrics09:26
witek_alternatively you can collect any Ceilometer or Prometheus measurements09:27
saskawitek_ : thank you. In the "per instance metrics" section I noticed 2 which may be helpful. mem.free_perc which is described as " Percent of memory free" and mem.resident_gb  which is described as "Total memory used on host, an Operations-only metric ". Does the first one refer to 1 VM (per instance== 1 VM)? What does it mean "operations-only metrics"?09:51
witek_saska: yes, instance = VM, this document describes the libvirt plugin09:59
witek_this plugin provides two sets of measurements, one for the operator (operator project) and one for the tenant10:00
witek_mem.resident_mb is available only in operator project10:01
witek_please also see this section https://github.com/openstack/monasca-agent/blob/master/docs/Libvirt.md#untunable-metrics10:02
saskawitek_ : thank you. The last link shows that for an administrator, metrics are collected per instance (in libvirt plugin) and for a user per tenant. And the vm.mem.resident_mb is available only for open stack operator since a user (owner of a tenant) does not need to know how many gb of memory does his project occupy on a host. Is that right?10:38
witek_exactly10:38
*** witek_ is now known as witek10:38
saskawitek_ : thank you. I appreciate your help.10:51
witeksaska: you're welcome, don't hesitate to ask more10:54
saskawitek: Thank you. I have many, but trying to figure out some of them on my own. What is the difference between vm.mem.total_mb and vm.mem.resident_mb? Is it possible, that a VM has allocated memory on more than 1 host?11:25
witekhere is libvirt documentation describing these values: https://www.libvirt.org/html/libvirt-libvirt-domain.html#virDomainMemoryStatTags11:34
witekmem.total_gb - AVAILABLE11:34
witekmem.resident_db - RSS11:35
*** saska has quit IRC11:54
*** rcernin has quit IRC12:25
*** tkajinam has quit IRC12:27
*** psachin has quit IRC12:47
*** psachin has joined #openstack-telemetry13:12
*** witek has quit IRC13:47
*** bengates has quit IRC13:57
*** witek has joined #openstack-telemetry14:04
*** bengates has joined #openstack-telemetry14:12
*** psachin has quit IRC14:52
*** tesseract has quit IRC16:40
*** bengates has quit IRC16:50
*** bengates has joined #openstack-telemetry16:51
*** witek has quit IRC16:52
*** bengates has quit IRC16:56
*** witek has joined #openstack-telemetry17:05
*** witek has quit IRC17:15
*** rcernin has joined #openstack-telemetry22:04
*** rcernin has quit IRC22:04
*** rcernin has joined #openstack-telemetry22:05
*** etp has quit IRC22:15
*** etp has joined #openstack-telemetry22:16
*** tkajinam has joined #openstack-telemetry22:56
*** dave-mccowan has joined #openstack-telemetry23:10
*** threestrands has joined #openstack-telemetry23:50

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!