[ceilometer][octavia][Victoria] No metrics from octavia loadbalancer
Adam Tomas
bkslash at poczta.onet.pl
Tue Apr 13 10:17:16 UTC 2021
OK. I have some progress. I created meters.d and pollster.d (in pollsters.d I’ve created octavia.yaml with sample type gauge and unit load balancer) and now I can see some measures, but only if load balancer exists or not. Is there any way to force dynamic pollster to ask for url v2/lbaas/loadbalancers/[ID]/stats?
Best regards
Adam
> Wiadomość napisana przez Thomas Goirand <zigo at debian.org> w dniu 12.04.2021, o godz. 21:40:
>
> On 4/12/21 3:24 PM, Adam Tomas wrote:
>> Hi,
>> Im trying to get metrics from octavia’s load balancer, but can’t get any (gnocchi metric list | grep loadbalancer not returning anything). How should I configure ceilometer to get metrics from octavia? Ceilometer asks neutron for load balancer metrics, and neutron responses „resource cannot be found” (and that is obvious, because Neutron LBaaS service is deprecated). How to force neutron to get these resources from Octavia?
>> I’ve tried to use
>> [service_providers]
>> service_provider = LOADBALANCERV2:Octavia:neutron_lbaas.drivers.octavia.driver.OctaviaDriver:default
>> in neutron.conf, but it doesn’t work either…
>>
>> Best regards
>> Adam
>>
>>
>
> Hi Adam,
>
> It's up to Ceilometer to report it. Do create the resource types, add
> this to /etc/ceilometer/gnocchi_resources.yaml (note: if you don't have
> such a file in /etc/ceilometer, copy it there from somewhere below
> /usr/lib/python3/dist-packages/ceilometer):
>
> - resource_type: loadbalancer
> metrics:
> network.services.lb.outgoing.bytes:
> network.services.lb.incoming.bytes:
> network.services.lb.pool:
> network.services.lb.listener:
> network.services.lb.member:
> network.services.lb.health_monitor:
> network.services.lb.loadbalancer:
> network.services.lb.total.connections:
> network.services.lb.active.connections:
>
> Then do a ceilometer db_sync to populate the Gnocchi resource types.
>
> I hope this helps,
> Cheers,
>
> Thomas Goirand (zigo)
More information about the openstack-discuss
mailing list