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

[Sensu 2.0] Document built-in filters and their actions #409

Closed
3 tasks
portertech opened this issue May 7, 2018 · 0 comments · Fixed by #896
Closed
3 tasks

[Sensu 2.0] Document built-in filters and their actions #409

portertech opened this issue May 7, 2018 · 0 comments · Fixed by #896
Assignees
Milestone

Comments

@portertech
Copy link
Contributor

portertech commented May 7, 2018

Document the Sensu 2.0 built-in event filters and their implicit :

From https://github.com/sensu/sensu-go/blob/master/backend/pipelined/filter.go

  • is_incident (allow)
  • has_metrics (allow)
  • not_silenced (allow)
@cwjohnston cwjohnston added the 2.x label May 18, 2018
@apaskulin apaskulin mentioned this issue Sep 1, 2018
17 tasks
@apaskulin apaskulin added this to the Sensu 2.0 milestone Sep 24, 2018
@apaskulin apaskulin added in progress Currently being worked and removed next-for-development labels Oct 1, 2018
@apaskulin apaskulin self-assigned this Oct 1, 2018
@apaskulin apaskulin added ready and removed in progress Currently being worked labels Oct 4, 2018
@apaskulin apaskulin added in progress Currently being worked and removed ready labels Nov 1, 2018
@apaskulin apaskulin added ready for review PR is ready to review and removed in progress Currently being worked labels Nov 2, 2018
@Blue0ctober Blue0ctober added the in progress Currently being worked label Nov 14, 2018
@apaskulin apaskulin removed the ready for review PR is ready to review label Nov 14, 2018
@Blue0ctober Blue0ctober removed the in progress Currently being worked label Nov 16, 2018
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 a pull request may close this issue.

4 participants