Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Documentation on next step #138

Open
wolfdancer opened this issue Dec 16, 2016 · 3 comments
Open

Add Documentation on next step #138

wolfdancer opened this issue Dec 16, 2016 · 3 comments

Comments

@wolfdancer
Copy link
Contributor

Based on feedback from new user who was pointed to this place, we should update the document to show:

  • How to create server-side monitoring configuration
  • How to write alarm criteria, especially make it clear that only the metric, not the status, can trigger alerts.
@luridmacro
Copy link

Any update on this? I too ran into this issue. RS intelligence is a new tool for the org. Thanks

@itzg
Copy link
Contributor

itzg commented Sep 19, 2017

@luridmacro I'm sorry, this issue fell off the radar. While re-establishing the context of the issue here are some pointers mentioned in the description:

The server-side agent configuration is described here:
https://developer.rackspace.com/docs/rackspace-monitoring/v1/tech-ref-info/server-side-agent-config-yaml/#agent-plugin-check

The section on the alarm language touches on the nuances of the criteria evaluation:
https://developer.rackspace.com/docs/rackspace-monitoring/v1/tech-ref-info/alert-triggers-and-alarms/#alarm-language

@luridmacro
Copy link

Thanks for the info. I'll take a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants