The ask.openstack.org website will be read-only from now on. Please ask questions on the openstack-discuss mailing-list, stackoverflow.com for coding or serverfault.com for operations.
| 2016-11-17 20:24:03 -0600 | received badge | ● Famous Question (source) |
| 2016-06-14 02:53:30 -0600 | received badge | ● Scholar (source) |
| 2016-06-14 02:53:26 -0600 | commented answer | ceilometer polling strange behaviour This solvs my doubts. Thank you Shaoman. |
| 2016-06-14 02:21:33 -0600 | received badge | ● Notable Question (source) |
| 2016-06-13 08:45:22 -0600 | commented answer | ceilometer polling strange behaviour Hi Shaoman, Thanks for your reply. Is there any place where configure this interval in nova? I only know instance_usage_audit_period to report information about instances. Regards, Pepe |
| 2016-06-13 05:11:53 -0600 | received badge | ● Popular Question (source) |
| 2016-06-10 10:34:27 -0600 | asked a question | ceilometer polling strange behaviour Hi everybody, I'm having a strange behaviour polling two sources (network.services.lb.active.connections & compute.node.cpu.idle.percent). Both have the interval configured in pipeline.yaml to 30 seconds but I'm getting samples of compute.node.cpu every 60 seconds. Samples for lb.active connections are being received at correct interval. AFAIK, compute samples are queried by ceilometer-agent-compute and lb.active by ceilometer-agent-central. So is there any difference in how each agent reads pipeline.yaml? Some info: Ubuntu Xenial / Mitaka Ceilometer 6.0.0 Nova 13.0.0 Neutron 8.1.0 Thanks all, Pepe |