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

Update aggregate plugins for Sensu 1.x #73

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

portertech
Copy link
Contributor

@portertech portertech commented Dec 17, 2018

Updated the Sensu Check Aggregate plugins for Sensu 1.x. This pull-request drops support for Sensu < 0.24.0, supporting only named aggregates.

Closes #19

Signed-off-by: Sean Porter <portertech@gmail.com>
Signed-off-by: Sean Porter <portertech@gmail.com>
Signed-off-by: Sean Porter <portertech@gmail.com>
Signed-off-by: Sean Porter <portertech@gmail.com>
Signed-off-by: Sean Porter <portertech@gmail.com>
Signed-off-by: Sean Porter <portertech@gmail.com>
@portertech
Copy link
Contributor Author

screen shot 2018-12-17 at 12 52 27 pm
screen shot 2018-12-17 at 12 53 39 pm

@portertech
Copy link
Contributor Author

Deploying an RC gem build and doing some testing.

@portertech
Copy link
Contributor Author

cloon

@majormoses majormoses self-requested a review December 18, 2018 02:03
Copy link
Member

@majormoses majormoses left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall looks good have one question about losing an existing feature that I think could be implemented and needs a changelog entry.

Let's also get a changelog entry under:

## [Unreleased]
### Breaking Changes
- ...

@@ -114,13 +107,6 @@ class CheckAggregate < Sensu::Plugin::Check::CLI
long: '--pattern PATTERN',
description: 'A PATTERN to detect outliers'

option :honor_stash,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we have honor_silence? I get that the api calls have been changed with the rename but I think we can still provide the same functionality right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rework would be necessary to capture the client and check associated with particular named aggregate results (which probably requires a bunch of assumptions).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, we just need to call that out as one of the breaking changes in the changelog then.

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

Successfully merging this pull request may close these issues.

2 participants