← Back to team overview

monasca team mailing list archive

Re: question about monasca-agent installation

 

Hi,

I removed the times part and it worked as expected. Is there a possibility
to lower the default 60 seconds evaluation period?



On Fri, Aug 21, 2015 at 4:12 PM, Bryant, Craig W (HP Cloud Service) <
craig.bryant@xxxxxx> wrote:

> The alarm expression “ avg(cpu.user_perc) > 5 times 2” requires that the
> threshold value be exceeded for at least two minutes before the alarm goes
> to the ALARM state. The default period is 60 seconds and the “times 2”
> means two 60 second periods. How long does it take for it to change? It
> should be between two and three minutes given that expression.
>
> Craig Bryant
> HPCloud Monasca
>
> From: Oğuz Yarımtepe <oguzyarimtepe@xxxxxxxxx>
> Date: Friday, August 21, 2015 at 6:27 AM
> To: Tim Kuhlman <tim.kuhlman@xxxxxx>
> Cc: "monasca@xxxxxxxxxxxxxxxxxxx" <monasca@xxxxxxxxxxxxxxxxxxx>
> Subject: Re: [Monasca] question about monasca-agent installation
>
> I followed the pip method and set the monasca agent manually at one of my
> vms and used the monasca docker instance  also for keystone url and monasca
> api url.
> I also created an alarm: avg(cpu.user_perc) > 5 times 2
>
> I run the below command to create a
> cpu load stress --cpu 2 --timeout 600
>
> I can see the alarms are created but there is a latency. Takes some
> minutes to see the alarm. How can i make it more real time or am i missing
> something?
>
> I checked the times of the two machines and they are same at tha docker
> side and at my vm.
>
>
> On Thu, Aug 20, 2015 at 6:36 PM, Kuhlman, Tim <tim.kuhlman@xxxxxx> wrote:
>
>> You have some options on how you install the agent. You can certainly
>> install with just pip install the Ansible role actually does this but in
>> addition runs monasca-setup for you. Using pip is discussed on this page,
>> https://github.com/stackforge/monasca-agent/blob/master/docs/Agent.md#installing
>>
>> The Ansible role can make things even easier in particular if you have
>> Ansible installed. The playbook you call this from can be quite simple,
>> here is one I use:
>>
>> - *name*: Installs the Monasca Agent
>>
>>
>>
>>   *hosts*: monasca
>>
>>
>>
>>   *sudo*: yes
>>
>>
>>
>>   *vars*:
>>
>>
>>
>>     *monasca_agent_check_frequency*:15
>>
>>
>>
>>   *roles*:
>>
>>
>>
>>     - {*role*: monasca-agent, *tags*:[agent]}
>>
>> The key thing to be aware of is that the requirements for the role which
>> are all listed in the README.md at
>> https://github.com/hpcloud-mon/ansible-monasca-agent
>> In the above example those requirements are defined in the group_vars.
>> --
>> Tim Kuhlman
>> Monitoring
>> HPCloud
>>
>> From: Monasca <monasca-bounces+tim.kuhlman=hp.com@xxxxxxxxxxxxxxxxxxx>
>> on behalf of Oğuz Yarımtepe <oguzyarimtepe@xxxxxxxxx>
>> Date: Thursday, August 20, 2015 at 8:07 AM
>> To: "monasca@xxxxxxxxxxxxxxxxxxx" <monasca@xxxxxxxxxxxxxxxxxxx>
>> Subject: [Monasca] question about monasca-agent installation
>>
>>
>> What is the right way to install monasca-agent? Using
>> https://github.com/hpcloud-mon/ansible-monasca-agent or pip install?
>>
>> How will the ansible cookbook be used? There is no main.yml to run the
>> cookbook. Anyone can give me an example?
>>
>> --
>> Oğuz Yarımtepe
>> http://about.me/oguzy
>>
>>
>
>
> --
> Oğuz Yarımtepe
> http://about.me/oguzy
>
>


-- 
Oğuz Yarımtepe
http://about.me/oguzy

Follow ups

References