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

Clarify YAML array syntax for agent.plugin checks via config file #37

Closed
2 of 7 tasks
itzg opened this issue Aug 23, 2017 · 3 comments
Closed
2 of 7 tasks

Clarify YAML array syntax for agent.plugin checks via config file #37

itzg opened this issue Aug 23, 2017 · 3 comments
Assignees
Milestone

Comments

@itzg
Copy link

itzg commented Aug 23, 2017

What do you want us to know about?

(Check all that apply.)

Report a documentation issue

  • 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

On the page/section https://developer.rackspace.com/docs/rackspace-monitoring/v1/tech-ref-info/server-side-agent-config-yaml/#agent-plugin-check

image

  1. The blog link is not linked properly
  2. While supporting a user I realized it would be helpful to clarify that YAML array/list/sequences require a comma separated list inside the square brackets. Passing a space separated list would seem intuitively correct, but results in a single argument passed to the script specified by file.
@cyrichardson
Copy link
Contributor

Please review changes based on issue #37 at
https://staging.developer.rackspace.com/build-1d0dc93f61/docs/rackspace-monitoring/v1/tech-ref-info/server-side-agent-config-yaml/ and let me know if #38 can be merged.

@cyrichardson
Copy link
Contributor

@itzg ^^

@itzg
Copy link
Author

itzg commented Aug 23, 2017

The changes in #38 look perfect. Thanks.

cyrichardson added a commit that referenced this issue Aug 23, 2017
* Fix issue #37 - broken link and add additional info

* Fix link and note
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants