git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AW: [metrics] [telemetry] [stein] cpu_util


He guys, we are working to address this issue of Ceilometer. The first PR
of a series that we are working on is the following:
https://review.opendev.org/#/c/677031/. The idea is to leverage Ceilometer
to enable operators/admins to create pollsters on the fly (without coding).

Reviews are welcome to help us get the first commit of the feature in.
Also, feedback and suggestions for further improvements.


On Fri, Oct 18, 2019 at 12:23 AM Rico Lin <rico.lin.guanyu at gmail.com> wrote:

> FYI, there's a new ML with similar topic:  [1]
>
> [1]
> http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010210.html
>
> On Mon, Sep 9, 2019 at 6:19 PM Tobias Urdin <tobias.urdin at binero.se>
> wrote:
>
>> The cpu_util is a pain-point for us as well, we will unfortunately need
>> to add that metric back
>> to keep backward compatibility to our customers.
>>
>> Best regards
>> Tobias
>>
>> On 9/9/19 11:37 AM, Blom, Merlin, NMU-OI wrote:
>> >  From Witek Bedyk <witold.bedyk at suse.com> on Re: [aodh] [heat] Stein:
>> How to create alarms based on rate metrics like CPU utilization?
>> > Fr 16.08.2019 17:11
>> > '
>> > Hi all,
>> >
>> > You can also collect `cpu.utilization_perc` metric with Monasca and
>> trigger Heat auto-scaling as we demonstrated in the hands-on workshop at
>> the last Summit in Denver.
>> >
>> > Here the Heat template we've used [1].
>> > You can find the workshop material here [2].
>> >
>> > Cheers
>> > Witek
>> >
>> > [1]
>> >
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_sjamgade_monasca-2Dautoscaling_blob_master_final_autoscaling.yaml&d=DwICaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=hTUN4-Trlb-8Fh11dR6m5VD1uYA15z7v9WL8kYigkr8&m=KDzBi0a41i4kfZG7LrvMjx6tKJCAZHM71I9snAHtDbU&s=wZLSXjvqYiPmMVbz8fgezCE1iwxZcQXRe3zZZW1JBFo&e=
>> > [2]
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_sjamgade_monasca-2Dautoscaling&d=DwICaQ&c=vo2ie5TPcLdcgWuLVH4y8lsbGPqIayH3XbK3gK82Oco&r=hTUN4-Trlb-8Fh11dR6m5VD1uYA15z7v9WL8kYigkr8&m=KDzBi0a41i4kfZG7LrvMjx6tKJCAZHM71I9snAHtDbU&s=M1D9BENrKX7HD43HfcYFuB8vdP9fKgAuGOTXtRq5aZI&e=
>> > '
>> >
>> > Cheers
>> > Merlin
>> >
>> > -----Ursprüngliche Nachricht-----
>> > Von: Budai Laszlo <laszlo.budai at gmail.com>
>> > Gesendet: Freitag, 16. August 2019 18:10
>> > An: OpenStack Discuss <openstack-discuss at lists.openstack.org>
>> > Betreff: [metrics] [telemetry] [stein] cpu_util
>> >
>> > Hello all,
>> >
>> > the release release announce of ceilometer rocky  is deprecating the
>> cpu_util and *.rate metrics
>> > "* cpu_util and *.rate meters are deprecated and will be removed in
>> >    future release in favor of the Gnocchi rate calculation equivalent."
>> >
>> > so we don't have them in Stein. Can you direct me to some document that
>> describes how to achieve these with Gnocchi rate calculation?
>> >
>> > Thank you,
>> > Laszlo
>> >
>>
>>
>>
>
> --
> May The Force of OpenStack Be With You,
>
> *Rico Lin*irc: ricolin
>
>

-- 
Rafael Weingärtner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20191018/9e21e39d/attachment.html>