You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug (misspellings, grammatical problems, broken link, format issues)
Missing information
Incorrect information
Feedback or suggestions
Other
Product
Product bug
Product feedback
Note: For product-related issues, you can also submit an issue from the Rackspace Community Forum website.
Tell us more about your issue
I see dead page on https://developer.rackspace.com/docs/rackspace-monitoring/v1/api-reference/check-operations/#check-operations
Under "Create a check" section: Create a new check in the monitoring system by using a valid set of attributes from the checks attributes table. For a tutorial on creating some basic checks, see Create checks in the Rackspace Cloud Monitoring Getting Started Guide.
"Create checks" link is giving "Page Not Found" error.
Be as specific as possible. Include excerpts from the text or a screen capture when necessary.
The text was updated successfully, but these errors were encountered:
What do you want us to know about?
(Check all that apply.)
Report a documentation issue
Product
Note: For product-related issues, you can also submit an issue from the Rackspace Community Forum website.
Tell us more about your issue
I see dead page on https://developer.rackspace.com/docs/rackspace-monitoring/v1/api-reference/check-operations/#check-operations
Under "Create a check" section: Create a new check in the monitoring system by using a valid set of attributes from the checks attributes table. For a tutorial on creating some basic checks, see Create checks in the Rackspace Cloud Monitoring Getting Started Guide.
"Create checks" link is giving "Page Not Found" error.
Be as specific as possible. Include excerpts from the text or a screen capture when necessary.
![screen shot 2017-11-14 at 5 30 44 pm](https://user-images.githubusercontent.com/7436029/32814602-dc452a38-c964-11e7-9f68-2cd9c5055fd8.png)
The text was updated successfully, but these errors were encountered: