Create abstraction for Sensu Checks about sensu-plugin-sdk HOT 6 CLOSED

@fguimond @calebhailey I don't have access to this repository https://github.com/sensu-skunkworks/sensu-aws-ec2-deregistration-handler. Please provide me the access.

from sensu-plugin-sdk.

@sreejita-biswas - You can use this gist. Should be the same line numbers.
https://gist.github.com/fguimond/c4bfad1b6b6fe7165cdb4c028f4ecb73

from sensu-plugin-sdk.

@sreejita-biswas invite sent; see: https://github.com/sensu-skunkworks/sensu-aws-ec2-deregistration-handler/invitations

from sensu-plugin-sdk.

@fguimond please note the following comments/responses to your issue description:

1. "Handlers read a Sensu Event from stdin while Checks don't"

   Checks do not read stdin by default, but this is supported via the stdin check definition attribute; see https://docs.sensu.io/sensu-go/5.5/reference/checks/#spec-attributes (under "stdin"). Please note the following comments from the documentation:

   If the Sensu agent writes JSON serialized Sensu entity and check data to the command process’ STDIN. The command must expect the JSON data via STDIN, read it, and close STDIN. This attribute cannot be used with existing Sensu check plugins, nor Nagios plugins etc, as Sensu agent will wait indefinitely for the check process to read and close STDIN.

2. "Handlers can read input values from the event, while checks can't since they don't read an event"

   I'm not sure if I understand this assertion. Checks can read input values from the request payload if stdin is enabled, however, only the check configuration is available at this time (e.g. the configured check definition attributes).

3. "Checks write the return the result data to stdout or stderr, handlers don't"

   Handlers can and do generate standard output (stdout), and Sensu does consume this output, but handler stdout is currently only visible in the sensu-backend logs, and only when --log-level is set to debug (we don't currently display this anywhere in the web ui, however this will change soon).

4. "Checks exit status code indicates the state... 0=OK, 1=WARNING, 2=CRITICAL, other=UNKNOWN"

   Sensu also validates handler exit status codes to determine handler success; if a handler exits with a "non-zero" exit status code, Sensu logs an error. As above, this is currently only observable in the sensu-backend logs and only when --log-level is set to debug.

I hope this helps! Let me know if you have any questions.

from sensu-plugin-sdk.

Thank you for the clarifications @calebhailey this is very helpful.

1. "If the Sensu agent writes JSON serialized Sensu entity and check data to the command process’ STDIN"

Would you happen to have a sample of such a structure? The Event consumed by the handler does contain a Check and an Entity but it also has Timestamp and Metrics. Is there a different data structure used for checks?

Thank you!

from sensu-plugin-sdk.

Sensu Go Plugin Library

from sensu-plugin-sdk.