unable to specify time constraints for alarms

Bug #1288246 reported by Nejc Saje
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-ceilometerclient
Fix Released
Undecided
Uros Jovanovic

Bug Description

Time constraints for alarms cannot be specified with Ceilometer CLI

Changed in python-ceilometerclient:
assignee: nobody → Uros Jovanovic (uros-jovanovic)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-ceilometerclient (master)

Fix proposed to branch: master
Review: https://review.openstack.org/78356

Changed in python-ceilometerclient:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-ceilometerclient (master)
Download full text (6.6 KiB)

Reviewed: https://review.openstack.org/78356
Committed: https://git.openstack.org/cgit/openstack/python-ceilometerclient/commit/?id=7146571b702579fa1367598ab278ca2f8ec1e156
Submitter: Jenkins
Branch: master

commit 7146571b702579fa1367598ab278ca2f8ec1e156
Author: Uros Jovanovic <email address hidden>
Date: Wed Mar 5 18:49:14 2014 +0000

    Adds alarm time constraint support to ceilometer CLI

    Time constraints can be specified for create and update
    families of commands with the following format:

    --time-constraint name=constraint1;start='0 11 * * *';duration=300

    This switch can be specified multiple times in the case of
    multiple time constraints.

    With update commands, time constraints are updated by name,
    e.g. --time-constraint name=constraint1;duration=500 updates
    the constraint 'constraint1' with a new duration 500.

    Time constraints can be removed with update commands using the
    switch --remove-time-constraint=constraint1,constraint2 .

    Example of display outputs:

    > ceilometer alarm-list
    +--------------------------------------+-------+-------------------+---------+------------+----------------------------+--------------------------------------------------------------+
    | Alarm ID | Name | State | Enabled | Continuous | Alarm condition | Time constraints |
    +--------------------------------------+-------+-------------------+---------+------------+----------------------------+--------------------------------------------------------------+
    | 2ead776d-2fc7-47a2-b0bb-0f88dcefa457 | test2 | insufficient data | True | False | cpu == 50.0 during 1 x 60s | cons1 at 0 11 * * * for 300s, cons2 at 0 23 * * * for 600s |
    +--------------------------------------+-------+-------------------+---------+------------+----------------------------+--------------------------------------------------------------+

    > ceilometer alarm-show -a
    +---------------------------+-----------------------------------------------------------------------+
    | Property | Value |
    +---------------------------+-----------------------------------------------------------------------+
    | alarm_actions | [] |
    | alarm_id | 2ead776d-2fc7-47a2-b0bb-0f88dcefa457 |
    | comparison_operator | eq |
    | description | Alarm when cpu is eq a avg of 50.0 over 60 seconds |
    | enabled | True |
    | evaluation_periods | 1 |
    | exclude_outliers | False |
    | insufficient_data_actions | [] ...

Read more...

Changed in python-ceilometerclient:
status: In Progress → Fix Committed
Changed in python-ceilometerclient:
milestone: none → 1.3.0
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.