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

Silencing entries are not working #1449

Closed
palourde opened this issue May 4, 2018 · 0 comments
Closed

Silencing entries are not working #1449

palourde opened this issue May 4, 2018 · 0 comments
Labels

Comments

@palourde
Copy link
Contributor

palourde commented May 4, 2018

Expected Behavior

I expect silenced events to not go through the pipeline, and therefore not be handled.

Current Behavior

Silenced events are currently handled!

$ date
Fri May  4 17:39:25 EDT 2018
$ sensuctl silenced list
         ID            Subscription     Check          Begin          Expire   ExpireOnResolve   Creator   Reason    Organization   Environment
 ─────────────────── ───────────────── ─────── ───────────────────── ──────── ───────────────── ───────── ───────── ────────────── ─────────────
  entity:i-424242:*   entity:i-424242           04 May 18 17:35 EDT   57m45s   false             admin     Testing   default        default
$ sensuctl event list
     Entity          Check        Output   Status   Silenced             Timestamp
 ────────────── ──────────────── ──────── ──────── ────────── ───────────────────────────────
  i-424242       check-random                   2   true       2018-05-04 17:39:37 -0400 EDT
# In sensu-backend logs:
{"component":"pipelined","environment":"default","handler":"slack","level":"info","msg":"event pipe handler executed","organization":"default","output":"","status":0,"time":"2018-05-04T17:37:37-04:00"}

And in Slack:
screen shot 2018-05-04 at 5 40 07 pm

Possible Solution

Steps to Reproduce (for bugs)

  1. Setup a check, with a handler
  2. Assign this check's subscription to a running agent
  3. Create a silencing subscription, with the begin field in a near future, e.g.
$ sensuctl silenced create \
--subscription 'entity:i-424242' \
--begin 'May 05 2018 9:34 UTC' \
--expire 3600 \
--reason 'Testing'
  1. Observe the sensu-backend logs

Context

Your Environment

  • Sensu version used (sensuctl, sensu-backend, and/or sensu-agent): master
  • Installation method (packages, binaries, docker etc.): manually
  • Operating System and version (e.g. Ubuntu 14.04): macOS 10.13.4
@palourde palourde added the bug label May 4, 2018
@palourde palourde changed the title Silencing entries with Begin are not working Silencing entries are not working May 7, 2018
@palourde palourde closed this as completed Aug 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant