pyrax
Python Bindings for the Rackspace Cloud
|
Handles all of the check-specific requests. More...
Public Member Functions | |
def | create_check |
Creates a check on the entity with the specified attributes. | |
def | update |
def | find_all_checks |
Finds all checks for a given entity with attributes matching ``**kwargs``. |
Handles all of the check-specific requests.
def create_check | ( | self, | |
label = None , |
|||
name = None , |
|||
check_type = None , |
|||
details = None , |
|||
disabled = False , |
|||
metadata = None , |
|||
monitoring_zones_poll = None , |
|||
timeout = None , |
|||
period = None , |
|||
target_alias = None , |
|||
target_hostname = None , |
|||
target_receiver = None , |
|||
test_only = False , |
|||
include_debug = False |
|||
) |
Creates a check on the entity with the specified attributes.
The 'details' parameter should be a dict with the keys as the option name, and the value as the desired setting.
If the 'test_only' parameter is True, then the check is not created; instead, the check is run and the results of the test run returned. If 'include_debug' is True, additional debug information is returned. According to the current Cloud Monitoring docs: "Currently debug information is only available for the remote.http check and includes the response body."
def find_all_checks | ( | self, | |
kwargs | |||
) |
Finds all checks for a given entity with attributes matching ``**kwargs``.
This isn't very efficient: it loads the entire list then filters on the Python side.
def update | ( | self, | |
check, | |||
label = None , |
|||
name = None , |
|||
disabled = None , |
|||
metadata = None , |
|||
monitoring_zones_poll = None , |
|||
timeout = None , |
|||
period = None , |
|||
target_alias = None , |
|||
target_hostname = None , |
|||
target_receiver = None |
|||
) |