The community from sensu-plugins

Create a sensu handler for iris (linkedin's open source pagerduty alternative)

We should keep our eye on if iris: https://github.com/linkedin/iris gains more popularity and if so we should probably minimally setup a repo based on the skel so if someone wanted to start using it they could start contributing to an official rather than needing to do a transfer later.

Create sensu-plugins-freeradius repo

Transfer ownership of plugin sensu-plugins-microsoft-teams to sensu-plugins organization

I would like to transfer the ownership of this plugin to the sensu-plugins organization in hopes of better community support and exposure. I have reviewed the skeleton plugin for best practices.

Repo to transfer:
https://github.com/tuxpower/sensu-plugins-microsoft-teams

I am also interested in continuing to help as a maintainer of this plugin 👍

Transfer of ownership of sensu-plugins-pdns to community

We would like to transfer the ownership of this plugin to the sensu-plugins organization in hopes of better community support and exposure. I have reviewed the skeleton plugin for best practices.

Repo to transfer:

https://github.com/haashah/sensu-plugins-pdns

I am also interested in continuing to help as a maintainer of this plugin 👍

Create sensu-plugins-strongswan repo

I am writing plugins for strongswan. Can you create the repo please.

RFE: First class VMware vSphere checks

FROM @jflemer-ndp - sensu/sensu#1527

Request For Enhancement: Provide a (public or enterprise) extension or plugin with first class monitoring of vSphere.

Expected Behavior

sudo sensu-install -p vsphere

Current Behavior

Maybe use Nagios plugins, pulling in associated dependencies, and JIT/Proxy checks:

https://github.com/jjasghar/esxi_health (Ruby)
https://github.com/rogerlz/nagios-check-vcenter (Python)
https://www.claudiokuenzler.com/nagios-plugins/check_esxi_hardware.php (Python)
https://github.com/lgeeklee/pyvinga (Python)

These are less desirable due to having to use JIT/Proxy and the need to deal with Python environment & deps in addition to Ruby.

Possible Solution

VMware provides a capable Ruby interface to the vSphere API (https://github.com/vmware/rbvmomi)
Implement a CLI check plugin that can be used as a JIT/Proxy check using rbvmomi
Implement an extension using rbvmomi that supports subscription based checks (but not actually requiring sensu-client on a ESXi/vSphere/VCSA node)

Context

Monitoring of hybrid infrastructure necessitates monitoring of the virtualization infrastructure to include:

hypervisor health (cpu, memory, uptime)
hypervisor networks
data stores
etc

Your Environment

Sensu 0.26
vSphere & vCenter 6.5 with VCSA

Transfer zfs sensu-plugins-zfs

Transfer Ownership

I would like to transfer the ownership of this plugin to the sensu-plugins organization in hopes of better community support and exposure. I have reviewed the skeleton plugin for best practices.

Repo to transfer: https://github.com/blacksails/sensu-plugins-zfs

Move flapjack handler over

Currently the Flapjack handler is still in the deprecated repo: https://github.com/sensu/sensu-community-plugins/blob/master/extensions/handlers/flapjack.rb I'm assuming it was not moved to favor the built in Sensu Flapjack handler, however per https://sensuapp.org/docs/latest/enterprise-built-in-handlers#flapjack built-in Flapjack appears to be an enterprise only feature. Please bring the external Flapjack handler back into the fold. Thanks.

Transfer ownership of plugin sensu-plugins-switchvox to sensu-plugins organization

We would like to transfer the ownership of this plugin to the sensu-plugins organization in hopes of better community support and exposure.

Per Slack convo I'll compare against https://github.com/sensu-plugins/sensu-plugins-skel to prep it for transfer

https://github.com/arineng/sensu-plugins-switchvox

Plugin Repo Skel

Is there a skeleton repo that can be copied from when creating a new repo?

@mattyjones @eheydrick

New plugin for working with dovecot

Hey hey,

i wrote a plugin to collect metrics from dovecot and i am wondering if you are interested in forking it into the sensu-plugins namespace. I would continue maintaining it.

See: https://github.com/ushis/sensu-plugins-dovecot

Cheers, ushi

Move to Slack as primary communication platform

The maintainers of Sensu Plugins and contributors from Sensu Inc have discussed adoption of a more user-friendly and easily accessible real-time communication platform for years. Since the group's decision to go into Maintenance Mode, we have moved to building out a Sensu Community Slack team that will meet these requirements.

Why

For many, Slack is the app where they participate in multiple communities - both open source and proprietary - on a regular basis. It also doesn't require you to be online to receive a response. The near universal adoption along with the ease of response are the two main reasons to make this move.

When

Effective immediately, we will recommend people join our Slack team by invite or through this landing page at slack.sensu-plugins.io. We will officially focus our developer/user real-time communication to Slack as of Sensu Summit on August 15, 2017.

Steps

Maintainers and some contributors have already joined the new Slack and began to build it into the multi-channel location they'd like it to be. Beyond that, we will do achieve the following before closing this issue:

Adjust Sensu, Sensu Plugin and Sensu Extension organizations to point users to Slack
Share this issue on IRC so others can note the move

Notes

Active maintainers of Sensu Plugins will have admin rights over the Sensu Community Slack.
We've considered costs associated with Slack and chosen to allow Sensu Inc to pay for the service, giving the org key features we will use
Also discussing costs, we considered how many pay for persistent IRC sessions or pay for server time to run an IRC service and how this choice takes that burden off of the community member

Transfer sensu-plugin-python to sensu-plugins org

Transfer Ownership

Following on from our discussions on slack, we would like to move the sensu-plugin-python repo over from sensu org to sensu-plugins org.

Repo to transfer: https://github.com/sensu/sensu-plugin-python

I am also interested in continuing to help as a maintainer of this plugin as is @luisdavim 👍

Create sensu-plugins-json-metrics repo

Sensu-Plugins-JSON-Metrics gathers metrics from any JSON metrics endpoint by traversing the
response and flattening the keys into a Graphite-compatible format, e.g.

{
  "just": {
    "a": {
      "test": 0
    }
  },
  "whats": [
    { "this": 0 },
    "oops",
    { "this": 1 },
    { "that": 2 }
  ],
  "another": 1
}

Will be converted to something like this:

hostname.metrics.just.a.test 0 1234567890
hostname.metrics.whats.0.this 0 1234567890
hostname.metrics.whats.1.this 1 1234567890
hostname.metrics.whats.2.that 2 1234567890
hostname.metrics.another 1 1234567890

In the most basic form, just shoot it at an endpoint:

$ metrics-json.rb --uri 'http://app.dev/v1/metrics.json' --scheme 'app.dev.metrics'

This plugin supports more advanced URIs, and there are a couple extra options
you may wanna check out:

$ metrics-json.rb \
  --convert-booleans \
  --replace-dots \
  --unknown-on-empty \
  --uri 'https://user:[email protected]/v2/metrics.json' \
  --scheme 'app.dev.metrics'

The plugin is currently hosted in a personal repository:
https://github.com/sczizzo/sensu-plugins-json-metrics

sensu-plugins-lvm repository

Hi,

Can a sensu-plugins-lvm repository please be created? I've created a check and a metric to monitor the free and used space in a volume group, modelled after the -disk- checks.

https://github.com/insom/sensu-plugins-lvm

I'm not certain on some of the packaging, but as with my Gearman repository have copied as much as possible from the existing sensu-plugins-* structure.

Transfer ownership of plugin sensu-plugins-stackstorm to sensu-plugins organization

Transfer Ownership

We would like to transfer the ownership of this plugin to the sensu-plugins organization in hopes of better community support and exposure. I have reviewed the skeleton plugin for best practices.

Repo to transfer: https://github.com/userlocalhost/sensu-plugins-stackstorm

I am also interested in continuing to help as a maintainer of this plugin 👍

If that's OK, I'll transfer the ownership of it to an owner (@majormoses) of this organization according to the instruction.

Clear Maintainers for Extensions

There is a Sensu Extensions org that does not have as much community stewerdship as the plugins do. I'd like to get our arms around whether:

we default to inviting plugin maintainers to also maintain extensions
who's best to champion this additional set of repos

Becoming a collaborator/maintainer

Hi,

I have been contributing with some PRs and code reviews but would like to be able to help with moderating (merging sane requests, releasing, etc) specially on the sensu-extensions org that seems to be lacking maintainers.

@mattyjones @portertech @majormoses

Create sensu-plugins-chatwork repo

Please create a repository for chatwork . Chatwork is a chat tool that can be used on the Internet .

Chatwork is here .
https://www.chatwork.com

Repository is here .
https://github.com/tsubauaaa/sensu-plugin-chatwork

New community plugin `sensu-plugins-routeros`

Create a repo with standard plugins skel for sensu-plugins-routeros to facilitate: x70b1/check_routeros-upgrade#2

Transfer ownership of plugin sensu-plugins-jolokia to sensu-plugins organization

We would like to transfer the ownership of this plugin to the sensu-plugins organization in hopes of better community support and exposure.

Per Slack convo I'll compare against https://github.com/sensu-plugins/sensu-plugins-skel to prep it for transfer

https://github.com/arineng/sensu-plugins-jolokia

Transfer Ownership of sensu-plugins-dcos

Transfer Ownership

We would like to transfer the ownership of this plugin to the sensu-plugins organization in hopes of better community support and exposure. I have reviewed the skeleton plugin for best practices.

Repo to transfer:
https://github.com/PTC-Global/sensu-plugins-dcos

I am also interested in continuing to help as a maintainer of this plugin 👍

Test runtime with ruby 2.4 on all repos

Basically sensu 0.29+ uses ruby 2.4 we need to start seeing what breaks horribly and prep for bumping sensu-plugin related to: #26

We shall generate a list of repos when we start planning this work as there are some repos are probably gonna be deprecated and some might have to be upgraded all the way to get it to install at runtime with ruby 2.4.

Transfer ownership of plugin sensu-plugins-signifai to sensu-plugins organization

Transfer Ownership

We would like to transfer the ownership of this plugin to the sensu-plugins organization in hopes of better community support and exposure. I have reviewed the skeleton plugin for best practices.

Repo to transfer: https://github.com/signifai/sensu-plugins-signifai/

I am also interested in continuing to help as a maintainer of this plugin 👍

We should make release cutting an automated process

There is imho way too much manual work being done in order to cut a release, I believe this is a major contributor to there often being very useful fixes and features added but have not been released.

I think we should simplify the release management to always cut a new tag and release on every pr to master. This means we can simply ensure that the submitter has the following:

bumped version accordingly with semver2 spec
Added their CHANGELOG entry; README if needed
Any code, tests, etc

If all goes well after maintainer review and merge it can be built without a maintainer having to pull down the repo, update CHANGELOG for missing entries, bump version, etc.

Rather than forcing the maintainers to do a bunch of manual steps that are of course error prone as we are terrible at following instructions where machines are great at doing exactly what we tell it. The other benefit is that users can immediately start pulling new changes if they want them. If we only had a few repos this would be less of an issue but we have a lots of repos. Also given the types of micro changes that typically happen in these projects it makes sense to me.

@mattyjones @portertech @eheydrick

Create a universal spec test plugin

migrating from https://github.com/sensu/sensu-summit-notes/issues/8

We currently have an rspec and serverspec plugin and we will soon have a inspec check. We should combine these all into a single plugin.

List of things to do:

Decide on a name, sensu-plugin-star-spec, sensu-plugins-test-spec, sensu-plugins-test-specs? Comment here to vote on naming.
Create new plugin (or rename one of the existing ones
Put deprecation notices in the readme and add a topic of deprecated
Remove all code from all the other repos and do a release which should make the most recent version of the gem contain no code. This should be versioned as a major.

Actionable Items from discussion on plugin pain points

migrated from https://github.com/sensu/sensu-summit-notes/issues/7

List of actionable Items from discussion on plugin pain points:

Testing

Integration testing of plugins on linux using: test-kitchen, kitchen-docker, and serverspec
Regression Testing across releases and platforms
A POC on performance testing
Document some ways to help users speed up their install time.
Scope better documentation on performance concerns and ways to solve them
RFC on Providing boilerplate code for embedding in debian/epel packages
RFC on Providing boilerplate code for embedding in geminabox packages
Create a gem to include all the common plugin tests to make it easy to update those in the future. @amdprophet

Windows

Scope out the most critical things people need in windows to be created. Currently there is a lack of windows plugins. As there are not any current maintainers that manage windows there will need to be some more heavy community contribution in order to scope and likely implement.
Create a powershell equivalent of sensu-plugin
Scope out what documentation is lacking
Windows integration testing with some CI tool other than travis

Best Practices

Scope out the different types of best practices documents and create issues for them:

Installing and pinning gems
Writing plugins
Sensu deployment Examples
Scaling Sensu
Improve CONTRIBUTING.md to have more information on what you should and should not include in a PR. For example you should not bump the version or date it as there is no guarantee on merge order nor is there an SLA on getting to it by EOD. Explain how a correct changelog entry should look. Update the PR templates with the same thing?

Misc

update readme in postgres plugin to reflect how to get this working with embedded ruby
Improve the skel to maybe have some example tests
Identify where we should add links for skel to so people can find it easier
Update the plugins with topics to make them more easily searchable

Create Best Practices Document for testing

migrating from https://github.com/sensu/sensu-summit-notes/issues/9

Basically write up how to write good tests and how the tests work:

types of testing and their effectiveness
testing platforms (start with linux, slowly add bsd, etc some like AIX will likely never be a thing
testing tools: travis, test-kitchen, kitchen-docker,(server|in)pec, rake, etc

Transfer ownership of plugin sensu-plugins-systemd to to sensu-plugins organization

Transfer Ownership

We would like to transfer the ownership of this plugin to the sensu-plugins organization in hopes of better community support and exposure. I have reviewed the skeleton plugin for best practices.

Repo to transfer: https://github.com/mickfeech/sensu-plugins-systemd

I am also interested in continuing to help as a maintainer of this plugin 👍

Merging community documentation into sensuapp.org/docs

Update: Dec 20

The new framework for documentation is visible here with source at sensu/sensu-docs-site. It includes the documentation listed below. We will check off each page once it's reviewed by any contributor -- please add a comment if you've reviewed a page!

Background

There's an effort at Team Sensu to get out of the middleman website that takes 30+ minutes to build to a faster, better organized and searchable Hugo service that was previewed at Sensu Summit. In this new build, there will be a section for Plugins specifically.

Proposal

I'd like to review existing documentation on http://sensu-plugins.io/docs (found in markdown here), decide if any pages should be deleted and which ones should be updated for migration. We can check off each document as we decide what to do with it.

Example of the upcoming redesign:

Shared serverspec gem

Shared serverspec gem. We talked.

Basic LDAP checks

In https://github.com/sensu-plugins/sensu-plugins-openldap, add a generic check, similar to the generic DNS checks.

bin/check-ldap.rb --ca-certificate xxx --certificate yyy --encryption start_tls \
  --host 127.0.0.1 --port 686 --bind-dn cn=foo --password abc \
  --base-dn dc=example,dc=com --query '(cn=foo)' --regex-match foo  --scope sub

Guidelines for contribution

There are a few universal practices that are worth documenting in this repository and possibly syndicating into all plugins within the organization:

Use of labels on issues/PRs
PR policies (style guides, staleness before closing)

I think it will be helpful to start with a document in this repository and then think about the right amount of information to sync to repos in the form of a CONTRIBUTING.md file.

Create sensu-plugins-nrpe repo

Please create a repository for sensu-plugins-nrpe. I created a check and a metric to monitor NRPE check results, modeled after the sensu-plugins-snmp repo.

https://github.com/scosist/sensu-plugins-nrpe

Transition to Community repository that documents maintainers

I'd like to transition this repo into a landing page for the community, similar to (though simpler than) the efforts of the Kubernetes, Docker, and Basho sites.

Test ruby install time with 2.4.1 on all repos

Basically sensu 0.29+ uses ruby 2.4 we need to start seeing what breaks horribly and prep for bumping sensu-plugin related to: #26,

I had started going through them ad-hoc for the last few weeks after merging requests but I think we need a bit more cadence on this so I pulled the list of remaining plugins and should circle back and update as we do this to bring some sanity to this madness.

remaining plugins:

Update scope of this repo

This repo is regularly used for migrating external plugins to this organization. It would be helpful to document that behavior in the README. It would also be good to remove unneeded code from here, especially with https://github.com/sensu-plugins/sensu-plugins-skel being the new home for a helper plugin.

Add integration testing for all the plugins repos

See example PRs linked below!

Becoming a collaborator/maintainer

What is the process for becoming a collaborator? I have been contributing where I can via code and review but would like to be able to help with moderating (merging sane requests, releasing, etc) the ever increasing amount of sensu issues.

@mattyjones @portertech

Bump all plugins dependency on `sensu-plugin` to 2.0

This is a breaking change and would be across all plugins and needs to be done with care, I see the following as a set of prerequisite before doing this:

ensure that all plugins can successfully build against ruby 2.4 (add testing of 2.4.1 to travis has been started)
ensure that all plugins can execute successfully against ruby 2.4

When we do this we leave behind all sensu installs of < 0.29 which while I don't have numbers to back me on are probably a majority of sensu installs so this should not be done lightly and will require at least 1 and in fair number of cases 2 breaking changes to every single plugin.

What this means for Sensu admins

Remember to always pin your Sensu system and your gems with specific versions
Be aware that 0.29 and above use Ruby 2.4 and plugins need to be compatible with this version
If you want to contribute please checkout #27, #29 and reach out to a maintainer if you have questions (@majormoses @eheydrick @mbbroberg)

EDIT: we should pin sensu-plugin to ~> 2.5 to pull in the latest and greatest.

Remove codeship from all repos

Remove codeship from all repos. We are no longer using it. These repos still have codeship enabled:

Kryten
documentation
sensu-plugins-bluepill
sensu-plugins-boundary
sensu-plugins-cgroups
sensu-plugins-clockworksms
sensu-plugins-conntrack
sensu-plugins-cucumber
sensu-plugins-dashing
sensu-plugins-eep
sensu-plugins-entropy-checks
sensu-plugins-erlang
sensu-plugins-execute
sensu-plugins-eye
sensu-plugins-filesystem-checks
sensu-plugins-ftp
sensu-plugins-geckoboard
sensu-plugins-gelf
sensu-plugins-github
sensu-plugins-gluster
sensu-plugins-golang
sensu-plugins-google-spreadsheet
sensu-plugins-gpg
sensu-plugins-growthforecast
sensu-plugins-gtalk
sensu-plugins-haproxy
sensu-plugins-hardware
sensu-plugins-hubot
sensu-plugins-icecast
sensu-plugins-iis
sensu-plugins-imkayac
sensu-plugins-ipmi
sensu-plugins-ipvs
sensu-plugins-librato
sensu-plugins-mackerel
sensu-plugins-messagemedia
sensu-plugins-monit
sensu-plugins-nbzget
sensu-plugins-netscaler
sensu-plugins-officehours
sensu-plugins-openldap
sensu-plugins-openstack
sensu-plugins-opentsdb
sensu-plugins-opsgenie
sensu-plugins-pacemaker
sensu-plugins-percona
sensu-plugins-pingdom
sensu-plugins-ponymailer
sensu-plugins-postfix
sensu-plugins-puma
sensu-plugins-qmail
sensu-plugins-rabbitmq
sensu-plugins-request-tracker
sensu-plugins-resque
sensu-plugins-rethinkdb
sensu-plugins-riak
sensu-plugins-rspec
sensu-plugins-selinux
sensu-plugins-sensu
sensu-plugins-sentry
sensu-plugins-sidekiq
sensu-plugins-sip
sensu-plugins-skyline
sensu-plugins-solr
sensu-plugins-splunk
sensu-plugins-springboot
sensu-plugins-statuspage
sensu-plugins-strongswan
sensu-plugins-syslog-ng
sensu-plugins-talker
sensu-plugins-telapi
sensu-plugins-tempodb

Create sensu-plugins-gearman repository

Hi,

I've created a set of basic gearman plugins modelled on the sensu-plugins-beanstalk repository - can a new repository please be created for it? I'm hosting it on my personal GitHub for now:

https://github.com/insom/sensu-plugins-gearman

Regards,

Aaron

Kubernetes Sensu Plugins Repo

Hello,

@kelcecil, @jmccarty3 and myself have developed a few Sensu plugins and a handler for Kubernetes and we were wanting to get a repo made for it so others can find it easily. The repo is currently located here:
https://github.com/nyxcharon/sensu-plugins-kubernetes

These checks have been in use in a production environment since the beginning of august or so.
Let me know if you need me to do anything or need any more information from me.

Update post install message

Currently when you install a plugin it outputs the message You can use the embedded Ruby by setting EMBEDDED_RUBY=true in /etc/default/sensu. This was helpful years ago before embedded ruby was enabled by default but now it can can be confusing as the message suggests you need to take action when none is required anymore.

EMBEDDED_RUBY=true was made the default in Sensu 0.21.0, which was released in 11/2015. The Chef cookbook and Puppet module default to EMBEDDED_RUBY=true as well.

Instead, we should say something like "Thanks for installing Sensu Plugins!"

new repo: sensu-plugins-vault

New Repo

We currently have sensu-plugins-consul. I'd like to be able to contribute my sensu plugin for hashicorp vault

Repo to create: sensu-plugins-vault

I am also interested in continuing to help as a maintainer of this plugin 👍

check-aggregate as a plugin

Currently check-aggregate.rb is in the deprected repo, and as far as I can tell it's the only decent aggregate check plugin. Can we build a gem for it? I'm happy to help if we can get a repo set up.

sensu-plugins-tomcat repository

Can you please create a sensu-plugins-tomcat repository, or allow me to transfer the current repo in my personal repo to the sensu plugins ORG https://github.com/smbambling/sensu-plugins-tomcat

I believe in the dev docs it stated I would have read/write access to this new repository as well, is that correct ?

Additionally I have several members of my team that we would want to have access to this repo as well, is that an issue ?

Transfer ownership of sensu-pg package

Transfer Ownership

I would like to transfer ownership of this "plugin" to the sensu-plugins organization in hopes of better community support and exposure. I have reviewed for best practices, but this is not standard ruby plugin, this is debian package with libpg support for embedded environment, which makes installation of pg gem possible. I will make same packages for rpm distros too.

Repo to transfer:
https://github.com/mrtrotl/sensu-pg.git

I am also interested in continuing to help as a maintainer of this plugin 👍

Please create a new repo 'sensu-plugins-gpg-keys-check'

Hi Sensu Community Plugins team,

I developed check-gpg-expiry.rb script which checks all public or secret GPG keys' expiry dates and sends appropriate alerts to Sensu client. I also developed check-gpg-expiry-spec.rb script which ensures that the check-gpg-expiry.rb script works properly.

I would like to contribute them to a new repo 'sensu-plugins-gpg-keys-check' in Sensu Community Plugins GitHub.

Could you please help to create a new repo in Sensu Community Plugins so that I can upload all my files to the repo.

Kind regards,
Aditya

Mailgun plugin repo

Hello,

I've made a sensu plugins repo for checks and metrics on Mailgun, and would like this to be made available to others. The repo is located at:

https://github.com/brendangibat/sensu-plugins-mailgun

Let me know what you need to get the repo in to sensu-plugins shape.

Thanks!

@sstarcher

sensu-plugins / community Goto Github PK

community's People

Contributors

Stargazers

Watchers

Forkers

community's Issues

Expected Behavior

Current Behavior

Possible Solution

Context

Your Environment

Transfer Ownership

Why

When

Steps

Notes

Transfer Ownership

Transfer Ownership

Transfer Ownership

Transfer Ownership

Testing

Windows

Best Practices

Misc

Transfer Ownership

Update: Dec 20

Background

Proposal

Bump all plugins dependency on sensu-plugin to 2.0

What this means for Sensu admins

New Repo

Transfer Ownership

Recommend Projects

Recommend Topics

Recommend Org

Bump all plugins dependency on `sensu-plugin` to 2.0