Skip to content
This repository has been archived by the owner on Apr 8, 2022. It is now read-only.

Granular and Extended Event Alerting #105

Open
tylerauerbeck opened this issue May 3, 2018 · 3 comments · May be fixed by #155
Open

Granular and Extended Event Alerting #105

tylerauerbeck opened this issue May 3, 2018 · 3 comments · May be fixed by #155
Labels
enhancement

Comments

@tylerauerbeck
Copy link
Contributor

There have been a few requests to be able to be very specific about what types of events kubewatch alerts on.

For example, rather than being alerted of all events when you subscribe to an object like pods, you may just be interested in a single action (create,update,delete). So we may want to have our yaml file look something like:

resource:
  deployment: true
    events:
      update: true
  replicationcontroller: false
  replicaset: false
  daemonset: false
  services: false
  pod: true
  job: false
  persistentvolume: false
  namespace: true
    events:
       delete: true
  node: false

There are also some types of objects that have a larger series of events, such as jobs. Specifically for the Job type, it may be interested to see whether the job completed successfully or if it failed.

This issue is to discuss

  • How best to implement the subscription of specific events rather than all events of an object
  • Is it a goal of Kubewatch to subscribe to these extended events or to just cover the normal create,update,delete events? If we are interested in the extended events, what's the best way to accomplish this?
@tylerauerbeck
Copy link
Contributor Author

cc/ @aananthraj @PavelKarpenka

@tylerauerbeck
Copy link
Contributor Author

This is an extension of #43, so we'll close that issue and have the discussion here.

@tylerauerbeck tylerauerbeck mentioned this issue May 3, 2018
Closed
akshaychitneni added a commit to akshaychitneni/kubewatch that referenced this issue Nov 11, 2018
@akshaychitneni
Granular and Extended Event Alerting
00cf01f 
fixes vmware-archive#105

This feature adds support to alert on specific event type per resource.
For example, to watch only create and update events on deployment resource, kubewatch.yaml should be
 resource:
  deployment:
    watch: true
    events:
      create: true
      update: true
      delete: false
This also adds custom event type 'loadbalancercreate' to notify when there is a loadbalancer created for a service.
 resource:
  services:
    watch: true
    events:
      create: true
      update: true
      delete: true
      loadbalancercreate: true
@akshaychitneni akshaychitneni linked a pull request Nov 11, 2018 that will close this issue
Open
unbreakab1e pushed a commit to joomcode/kubewatch that referenced this issue Mar 5, 2019
@akshaychitneni @unbreakab1e
Granular and Extended Event Alerting
69cca93 
fixes vmware-archive#105

This feature adds support to alert on specific event type per resource.
For example, to watch only create and update events on deployment resource, kubewatch.yaml should be
 resource:
  deployment:
    watch: true
    events:
      create: true
      update: true
      delete: false
This also adds custom event type 'loadbalancercreate' to notify when there is a loadbalancer created for a service.
 resource:
  services:
    watch: true
    events:
      create: true
      update: true
      delete: true
      loadbalancercreate: true
@codenio codenio mentioned this issue Jun 7, 2019
Open
@codenio
Copy link
Contributor

codenio commented Jun 10, 2019

@tylerauerbeck can we continue this discussion here or in #176 ?

@davidpristovnik davidpristovnik mentioned this issue Sep 18, 2019
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
2 participants
@tylerauerbeck @codenio