-
Notifications
You must be signed in to change notification settings - Fork 4
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 Sensu Entity Manager #154
Conversation
One subscription per line. | ||
|
||
``` | ||
system/linux |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
weird formatting of readme inside all the block quotes when rendered by the Catalog ui. Catalog UI is adding extra indention for the first line. Catalog UI bug maybe?
Only workaround i can manifest is to add a blank line at the top of the block quote.
Not actionable here.
- "@sensu" | ||
- "@calebhailey" | ||
prompts: | ||
- type: section |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to convert this section to using the optional secrets pattern like in elasticsearch integration
secret: entity-manager-api-key | ||
|
||
--- | ||
type: Secret |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to remove this Secret defintion as part of hte refactor to use env vars with optional secrets
The Sensu Entity Manager integration provides automated management of agent subscriptions, labels, and annotations. | ||
|
||
The Sensu Entity Manager works with any check or event producer that generates one instruction per line of `event.check.output` in any of the following formats: | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to add a section here mentioning what resources will be created on install
Event processing pipeline for auto-discovery workflows.