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

support for redis as a transport #639

Merged
merged 1 commit into from
May 30, 2017
Merged

support for redis as a transport #639

merged 1 commit into from
May 30, 2017

Conversation

RiRa12621
Copy link
Contributor

@RiRa12621 RiRa12621 commented Apr 18, 2017

this fixes #556

this work is heavily based on the work of @raffraffraff

this should be supported ASAP

@gutmensch
Copy link

LGTM

@lgarciaaco
Copy link

This is awesome!!

@@ -196,6 +196,11 @@
# Boolean. Reconnect to Redis in the event of a connection failure
# Default: true
#
# [*transport_types*]
# String. Transport type to be used by Sense
Copy link

Choose a reason for hiding this comment

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

This should probably say Sensu rather than Sense.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

maybe

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

@cwjohnston
Copy link
Contributor

Hi @RiRa12621, thanks for the pull request. This implementation seems reasonable, but I'd like to point out a few things for those following this PR.

  • There are unresolved issues with the Redis transport which make it less than suitable for production, i.e. duplication of check requests. As a result we recommend the Redis transport be used only in testing and development scenarios.

  • Sensu 0.19 is now almost two years old by now, and no longer available from the official Sensu package repositories. Anyone using a version prior to 0.23 is susceptible to Heartbleed, among other vulnerabilities.

  • The next release of this module will include other changes already merged to master which are thought to be incompatible with Sensu versions prior 0.27.

With regard to the last two points, I think its reasonable to remove logic guarding redis transport on Sensu < 0.19 as that code will most likely never be exercised.

@RiRa12621
Copy link
Contributor Author

Hey @cwjohnston,

  • I read about the issue with the duplicate check requests but that should not prevent from implementing the option, since even if it’s only for testing an pre-prod, also those machines might be / are managed by config management (puppet in this case)
  • even tho I am not a fan of making things backwards breaking, I see your point and can adjust that to remove Sensu < 0.19 support

removing trailing whitespaces

support for redis as a transport
@RiRa12621
Copy link
Contributor Author

is there nay progress to be expected on this one ?
it’s been a month now

@raffraffraff
Copy link

raffraffraff commented May 24, 2017 via email

@RiRa12621
Copy link
Contributor Author

true actually

@jaxxstorm jaxxstorm merged commit e5c9e56 into sensu:master May 30, 2017
@jaxxstorm
Copy link
Contributor

jaxxstorm commented May 30, 2017

I've merged this for you.

I want to make it clear why this took so long.

  • This module is heavily relied on for people's monitoring systems. We have a responsibility to merge good code, and review it thoroughly. This takes time.
  • This is a part time gig for me, I have a job that I need to do as well as maintain multiple open source projects

I understand the frustration here, but please try and be patient. I am not ignoring you.

@shajithravi
Copy link

@jaxxstorm any updates on this?

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

Successfully merging this pull request may close these issues.

Doesn't create a transport.json file
8 participants